Sequential chain registry

ABSTRACT

Systems and methods are disclosed for tracking an object as it traverses a sequential chain. The relationships between the object, its movement through space and time, and the entities associated with the object at a discreet point of time are captured by a sequential chain. A unique identifier may be created that is continuously modified as the object traverses the sequential chain. The unique identifier may be used to capture relationship information between the object and its related entities and movements.

PRIORITY

This application is a continuation of U.S. Pat. No. 8,819,026, entitled“Sequential Chain Registry,” filed on Aug. 25, 2011, which applicationclaims priority to U.S. Provisional Patent Application No. 61/377,809,entitled “Sequential Chain Registry System and Method,” filed on Aug.27, 2010, and is related to U.S. Pat. No. 8,918,430, entitled“Sequential Chain Registry for Event Awareness,” filed on Aug. 25, 2011,each of which are hereby incorporated by reference in their entirety.

BACKGROUND

It is often desirable to track an object as it traverses a sequentialchain. For example, a consumer product begins as raw materials, whichare then transported to a manufacturer that constructs a component ofthe consumer product using the raw materials. The component may then betransported to another manufacturer who constructs the consumer productusing the component. The consumer product may then pass through anynumber of distributors until it reaches a retailer and, finally, the endconsumer.

Because the consumer product, and the components and raw materials thatmake up the product, generally pass through so many differentmanufacturers that are often not related, it is difficult to track theproduct and its components as they travel through a supply chain orother form of sequential chain. It is even more difficult to trackmaterials to which a barcode, RFID, or other tracking mechanism cannotcontinuously be physically attached as materials transit supply or otherforms of chains. However, information related to products, componentsand raw materials is often desirable to consumers (for example,consumers who may be interested in tracking the origins and otherattributes of products they purchase) and to regulators (for example,regulators who may want to ensure that the materials used to make theproducts are used legally).

SUMMARY

Embodiments of the present disclosure relate to systems and methods forthe creation of a digital sequential chain that may be used to trackobjects as they traverse a sequential chain. In embodiments, thesequential chain relates object data, movement data, and entity data ina way that all of the movements and transformations that are performedon a product may be captured from the transition of the product from araw material to its final form. In further embodiments, the sequentialchain may also be applied to track intangible objects as they traverse asequential chain. Furthermore, the embodiments disclosed herein areflexible enough to track both structured and unstructured data.

In embodiments, a unique identifier, such as a DocString identifier iscreated that may be modified to track the relationship between one ormore objects, the traversal of the one or more objects through space andtime, and the relationship(s) between an object and one or more entitiesat each discrete time period. In such embodiments, the unique identifiermay be continually modified in order to capture relationships as theobject traverses the sequential chain.

Embodiments of the present disclosure also relate to providing a userinterface that may be used to provide the data for constructing asequential chain. Yet another embodiment discloses analytics that may beperformed on data obtained from the sequential chain and a userinterface for conveying the results of such analysis.

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

The same number represents the same element or same type of element inall drawings.

FIG. 1 is a flowchart illustrating an embodiment of a next step taken bya system facilitator, by system users or by another for designing adatabase structure for an embodiment of the SCR system and method.

FIG. 2 is an illustration depicting embodiments of database entities.

FIG. 3 shows example embodiments of entity relationships amongst threeexemplary entities.

FIG. 4 provides an example embodiment of a sequential chain (SC) thatmay be represented using the components described herein.

FIG. 5 is a block diagram depicting embodiments of relationshipsamongst: a sequential chain component; a host entity that hosts the SCcomponent; an object that exists in the SC component; and a documentthat contains data pertaining to the object as the object existsrelative to the SC component.

FIG. 6 illustrates the manner in which, in embodiments, a group, or set,of a plurality of such SC component-specific data sets may be formed.

FIG. 7 is a block diagram illustrating an embodiment of a data set thatmay be organized and compiled within an SCR database for a particularobject as it transits a sequential chain and/or as it changes its formduring the transit.

FIG. 8 is a block diagram illustrating an embodiment of a sequentialchain construction of a particular class of SC component with thefunctionality of a blend platform.

FIG. 9 is a block diagram illustrating an embodiment of a sequentialchain construction by a system designer or another of a particular classof SC component with functionality of a split platform.

FIG. 10 is a block diagram illustrating an embodiment of dualfunctionality (e.g., a combination of the blend and split platforms) ofa SC component.

FIG. 11 is a block diagram illustrating another feature of a data schemathat may be employed in an SCR embodiment.

FIG. 12 is a block diagram illustrating formation of a DocStringidentifier and the relation of the DocString identifier to an uncoveredobject, which is given unique identity by such form of objectidentifier.

FIG. 13 illustrates an exemplary format in which a DocString identifiermay be stored in an SCR database table.

FIG. 14 shows an exemplary instance of application of a DocStringidentifier.

FIG. 15 is an embodiment of a data entry form for enabling an SCRdatabase to receive data.

FIG. 16 is a flow chart illustrating an example embodiment of a methodto create a DocString identifier.

FIG. 17 is a flow chart illustrating an embodiment of a method forconstructing and operating on a sequential chain.

FIG. 18 is a block diagram illustrating components of an exampleembodiment of an SCR system.

FIG. 19 is a block diagram illustrating an exemplary embodiment of anSCR application in an environment wherein SCR database may receive datafrom either of, or both, an enterprise data system and a global datasynchronization network.

FIG. 20 illustrates one example of a suitable operating environment inwhich one or more of the present embodiments may be implemented.

FIG. 21 is an embodiment of a user interface illustrating data outputfrom a data analysis module, which may be included in an SCR embodimentfor the oil and gas industry.

FIG. 22 is a screenshot illustrating other exemplary data output from adata analysis module, which may be included in an SCR embodiment for theoil and gas industry.

FIG. 23 is a block diagram illustrating flows of data, as received byand returned from an SCR database for an embodiment of the SCR systemand method.

FIG. 24 illustrates an exemplary sequential chain.

FIG. 25 illustrates another exemplary sequential chain.

FIG. 26 illustrates additional exemplary sequential chains.

FIG. 27 illustrates three exemplary sequential chains and relationshipsbetween and among them.

FIG. 28 illustrates a plurality of sequential chains that, together,function in a combined chain mode.

FIG. 29 provides an example of data analysis that may be performed in acombined chain mode.

FIG. 30 provides an exemplary method for deriving and providing asequential chain data score according to embodiments of the presentapplication.

DETAILED DESCRIPTION

Embodiments of the present disclosure relate to procedures by which tomake and use a Sequential Chain Registry, referred to herein as SCR orthe SCR system and method; a non-limiting plurality of embodiments forthe SCR system and method; and non-limiting examples of data types anddata sources that may be used for data input to an embodiment. “SCR,”“SCR system,” and “SCR system and method” may also herein be usedgenerally to describe any disclosed embodiments of the presentapplication, and use of such terms is not intended to limit thedisclosure hereof or any resulting claims that assert priority hereto.In addition, although particular methods and processes may be disclosedas being performed, in examples, by particular systems, persons, orstructures, it is understood that such method steps may be performed byany combination of other systems, persons, or structures withoutdeparting from the scope hereof.

In embodiments, a “Sequential Chain Registry” enables suppliers,customers and other users of SCR to preserve and access data created, orcapable of being created, within both complex and simple sequentialchains. For example, non-limiting examples of a sequential chain mayinclude a supply chain, a chain of events, a chain of manufacturingprocesses, the transportation of a product, or any other type of eventor set of events in which an object is changed and/or transported over atime period. In embodiments, SCR may comprise a database-groundedprocedure, process, system, and/or method whereby particular objects maybe tracked and traced as those objects exist in and move through anynature of sequential chain, including parts, or components, of asequential chain. As used herein, the term sequential chain may alsoinclude, without limitation, any of supply chain, value chain, processchain, logistics chain or other nature of simple or complex group ofprocesses, pathway, or pathways by which an object exists (or objectsexist) in, moves through, and may be altered within one or a pluralityof components comprising such chains. Without limitation, the termsequential chain may also apply to circumstances wherein an object (forinstance, but not limited to, an oil or gas well) may not be a movingobject that transits a sequential chain, but rather may be a stationaryobject (e.g., a non-moving object) that may be operated upon via aplurality of processes contributing to the status, nature, size,description or other dimension, without limitation, of such object at aparticular time (e.g., as a set of particular oil well drillingprocesses and tasks contribute to drilling and completion of an oilwell, which may exist in a stationary condition, e.g., in a fixed locuswhere such well has been drilled and completed). In embodimentsinvolving moving objects—that is, with objects that transit through asequential chain—system users may be interested in particular types ofdata and information, as these may pertain to dimensions of time and/orspace in which moving objects exist in and transit through sequentialchains. In embodiments involving stationary, or non-moving, objects,system users may be interested in particular types of data andinformation, as these may pertain to: i) space, with respect to theparticular space, or locus, in which such stationary object may exist;and, ii) time, including with respect to temporal relationships that maydescribe temporal sequences in which two or a plurality of events orevent executions may occur in connection with particular processesoperating upon such stationary object or objects. Further discussions ofsequential chains and object(s) are provided below.

In embodiments, a registry may include an architected database systemwherein a database is capable of receiving data from one or a pluralityof users. Without limitation, such data may give unique identificationto a sequential chain and to a plurality of components comprising asequential chain. Such elements, or components, of a sequential chainare characterized by systems and/or users as relating to one another,such that a database may receive and store data in a manner that allowslogical relations to be established between: an object in a particularcomponent of a sequential chain; each such component to each other suchcomponent of a sequential chain; and other elements, as herein furtherdescribed. In embodiments as will be further described below, databaseentity relationships may be established and maintained between objectsand their various forms as they transit a sequential chain, supply chaincomponents that make up the sequential chain, supply chain componenthost entities and/or sub-entities that may define each supply chainhost, and between sequential chains themselves.

The sequential chain may be used to track data related to the changes ofan object, both physically (e.g., by physical and/or chemicalmanipulation of the object) and through space (e.g., the transportationof the object), as the object proceeds through a chain of processes orevents (e.g., a supply chain). Tracking such data enables enterprises tocapture a variety of forms of information pertaining to products (bothtangible and intangible) as the products make their way through complexglobal supply chains, enter into trade or commerce, and/or pass throughvarious intermediaries until products eventually reach downstreamintermediate and/or final customers. As will be described in more detailbelow, the sequential chain registry is capable of storing any type ofinformation related to the object as it progresses though a processand/or transaction changes.

The reference herein to “sequential chain registry system and method”employs the term “sequential” from this notion, or construct, of asequential chain component-centered data set, acting as a hub, thataccretes over time into a larger data set as an object sequentiallymoves within a uniquely identified sequential chain through a pluralityof uniquely identified sequential chain components. A sequential chainmay be registered in the registry. Registration of the sequential chainin a registry (e.g., a database or other software environment) allowsfor the association of a unique identifier with the SC. Registration ofthe sequential chain thereby allows the sequential chain: a) to possessa unique identity; and b) to “hold” or “house” a plurality of sequentialchain components (e.g., data related to a process or change that mayoccur during the sequential chain) by relating the sequential chaincomponents using the unique identifier. The ability of the registeredsequential chain to house the sequential chain component data allows forthe gathering of information related to an object as it traverses asequential chain.

In embodiments, a sequential chain may include the system oforganizations, people, technology, activities, processes, informationand resources involved in moving a product, service, or other form ofobject from supplier to customer. By way of non-limiting example,sequential chain activities, or processes, may include transformation ofnatural resources, raw materials and other elements into a finishedproduct that is delivered to customers, including intermediate and endcustomers. A sequential chain may begin with the human extraction of rawmaterial, and includes several production links (e.g., componentconstruction, assembly, and merging) before moving to elements such asstorage facilities, and finally reaching the consumer.

Presently, it is easier to track objects that are packaged. For example,a can of tuna can be easily tracked because a barcode or an RFID may beplaced on the packaging. However, unpackaged objects prove to be muchmore difficult to track as they progress along a supply chain. Forexample, a bar code or RFID may not readily be placed on a live tuna, amolecule of oil that is travelling through a pipeline, or an intangiblefinancial instrument. Furthermore, the unpackaged objects may be mixedwith other unpackaged objects (e.g., the molecule of oil from one oilfield is mixed with oil from another oil field as it is introduced intothe pipeline or commingled in storage tanks). As will be demonstratedthroughout this disclosure, the embodiments described herein overcomethe problems related to tracking unpackaged products. Furthermore, oneof skill in the art will appreciate that the systems and methodsdisclosed herein may be practiced with packaged objects as well. Forexample, nearly all packaged goods are at some point unpackaged orcontain previously unpackaged components. The SCR systems and methodsherein provide for a continuous identifier that can track an objectand/or its components prior to being packaged and having affixed to it aphysical identifier. In embodiments, the physical identifier may bebased on or become a part of the SCR identifiers disclosed herein toprovide continuous identification.

An unpackaged object may be referred to as an uncovered object. Inembodiments, uncovered objects include objects, including both tangibleand intangible objects and including services and the like, that are nototherwise amenable to tracking and tracing by existing systems based onexisting forms of object unique identifiers. Also as used herein,covered objects include objects that are not uncovered objects. SCRenables access to information pertaining to both uncovered and coveredobjects and to the sequential chains, the sequential chain components,and the surroundings of sequential chain components in which theseobjects exist, have existed or may exist.

In embodiments, both covered and uncovered objects may be identifiedusing an object unique identifier. An object unique identifier, alsoreferred to herein as a document string identifier or DocStringidentifier, may be used to give object unique identification touncovered objects. In embodiments, the DocString identifier, as it maybe created within the SCR system and method, enables uncovered objectsto be given object unique identification throughout sequential chains.Absent such DocString identifier, such uncovered objects may nototherwise be amenable to tracking and tracing continuously throughoutsequential chains. In embodiments, the structure of the SCR system andmethod, including its capability to form a DocString identifier forgiving unique identity to uncovered objects, enables a database in anSCR embodiment to receive, store, manipulate, and return more data andinformation pertaining to objects than may otherwise be possible viaexisting tracking and tracing systems and existing forms of objectunique identifiers (such as barcodes and RFIDs).

In embodiments, a DocString identifier may be created in conjunctionwith other operations of the SCR system and method. Once it is createdwithin an SCR database, a DocString identifier may be used to enablecontinuous identification of uncovered objects throughout sequentialchains, whereas uncovered objects otherwise may not be amenable to suchcontinuous identification. In embodiments, the SCR enables data storagein a database of a plurality of data attributes and data valuespertaining to: uncovered objects and trade documents associated withsuch objects; sequential chains in which such objects exist or mayexist; component segments of such sequential chains; the milieu orenvironment surrounding such component segments; and other data. On theother hand, embodiments also enable tracking and tracing uncoveredobjects through sequential chains by further enabling the formation of aform of object unique identifier—that is, formation of the DocStringidentifier—that enables the continuous identification of objects asthese objects exist in, and transit through, sequential chains. Whiledescribed with respect to tracking uncovered objects, in embodiments theDocString identifier may also be used to track covered objects.

While embodiments of the present disclosure have been described withrespect to tracking data related to objects as they traverse asequential chain, one of skill in the art will appreciate that theembodiments disclosed herein may be used to track and relate other typesof data. For example, the embodiments disclosed herein may be used toprovide event awareness by tracking structured or unstructured data asthey relate to a sequence of executed events and/or planned events inorder to relate data in such a manner that related events are tiedtogether.

SCR Data Types

Various different types of data (or SCR components) may be employed totrack an object and/or data related to an object as it traverses achain, such as, but not limited to, a supply chain. For convenience andillustration, but not by way of limitation, four defined data types, orcategories, are included in demonstrating the data that may be receivedby, and on which computation may be performed within, the SCR system andmethod. As used herein: i) data type-1, also referred to as object data,refers to data attributes and data values pertaining to an object thattransits a sequential chain; ii) data type-2, also referred to assequential chain (SC) data, refers to data attributes and data valuespertaining to a sequential chain; iii) data type-3, also referred to assequential chain component (SCC) data refers to data attributes and datavalues pertaining to a plurality of sequential chain components, whichcomprise a sequential chain; and iv) data type-4, also referred to assequential chain component host or host entity (SCC host or SCC hostentity) data refers to data attributes and data values pertaining to ahost entity that hosts a particular sequential chain component. Inembodiments, each of the SCR components described herein may also beassociated with an identifier. The identifier may be shared among theSCR components, for example, all of the different SCR components relatedin a sequential chain may have the same identifier, each SCR componentmay have its own unique identifier, or each SCR component may beassociated with both a shared identifier and a unique identifier.

In embodiments, object data may be used to represent an object, such asa covered object or an uncovered object. The object may be any type ofobject, including but without limitation tangible objects and intangibleobjects that traverse a sequential chain. As a non-limiting example,object data may represent oil as it traverses a supply chain. Objectdata may be extendable such that any type of data commonly associatedwith the covered or uncovered object represented by the object data maybe stored in the object data. This flexibility allows the SCR systemsand methods disclosed herein to be employed regardless of the type ofunderlying object that is being represented while allowing all relevantinformation associated with the object to be captured and stored. Inembodiments, objects may be dynamic; that is, objects may change duringthe sequential chain. For example, an object may start out as crudepetroleum and be refined into gasoline.

The SCC, in embodiments, is a data object capable of storing informationabout a sequential chain component. In embodiments, an SCC may representa component segment or element of an SC along with movement though timein which an object transits through an SCC that is associated with asequential chain. For example, an SCC may represent an oil field wherethe oil was first extracted, a pipeline movement of the oil, processingof the oil in a refinery, etc. In embodiments, an SCC may representanother SC. Although specific examples are provided, one of skill in theart will appreciate that SCC may represent information related to aprocess activity (e.g., a refinery or a chemical plant) or a change ofcontrol action (e.g., a pipeline or oil tanker).

As described above, an SC component (or SCC) may represent informationabout a particular point, process, conveyance or the like in thesequential chain. Data representing information about an entity relatedto the particular point, process, conveyance or the like in thesequential chain may be associated with an SCC. Such related data may bestored in one or more SCC host (or SCC host entity) objects. Inembodiments, multiple SCC host objects may be associated with a singleSCC, that is, the data for multiple entities may be related to a singleportion of time, e.g., an instance represented by a SCC, in thesequential chain. As non-limiting examples, a SCC may represent apipeline that oil is travelling through or a tanker carrying oil. Inturn, an example of a SCC host may be a country or other location inwhich is located a petroleum refinery, etc. SCC host objects may alsoinclude one or more SCC host sub-objects organized hierarchically orotherwise. For example, an SCC host object related to an SCC (e.g., arefinery) may be the country in which the SCC is located (e.g., theUnited Kingdom). An SCC host sub-object may comprise the city in whichthe SCC is located within the SCC host object (e.g., Milford Haven,Wales).

The sequential chain (SC) object, in embodiments, is a data objectcapable of grouping together and storing all other information (e.g.,object data, SCC data, SCC host data, etc.) that is related or relatablein a common sequential chain. The SC represents the entire sequentialchain, which is comprised of a plurality of SCCs. In embodiments, the SCmay be used to group and relate all information related to objects(e.g., object data) as they move through time and space as well as allof the entities associated with each discrete period.

Such information related to objects, SCs, SCCs, and SCC host entitiesmay be referred to as attributes. Any type of attribute may beassociated with the various data types disclosed herein. The sequentialchain registry systems and methods disclosed herein enable the capturingof any nature of SC Components (e.g., an oil producing field) as well asinformation related to an SC Host Entity (e.g., a country, region, oilfield name, and/or static or dynamic data further describing hostentities). In embodiments, attributes may be related to the objectsthemselves. In such embodiments, the attributes may contain informationrelated to quantity and/or quality measures of a product. Theembodiments disclosed herein provide ways of relating informationbetween objects, SC Components, and SC Host Entities thereby providing aflexible information profile related to an object and its hosts as ittraverses a sequential chain. For example, embodiments of SCR describedherein may utilize the relationships described herein to provide realworld information about an object traversing a supply chain, such as,but not limited to information demonstrating that a particular lotquantity of crude oil is produced or refined by one or more countriesthat practice “excellent” or “good” levels of Fiscal Transparency, asmeasured by an independent 3^(rd) party such as the ExtractiveIndustries Transparency Initiative, or EITI. Without the advent of SCR,such information may be lost as the supply of crude oil changes handsbetween different entities which have different, disparate data systemswhich cannot or may not communicate with one another.

In embodiments, the SC is an object that is assigned a unique identifierwhich differentiates a particular SC from any and all other SCs.Assigning a unique identifier to the SC may also be referred to as the“registration” of the SC. Thus, the registration of the SC in a registry(e.g., a database or other software environment) allows for theassociation of a unique identifier with the SC. Registration of the SCthereby allows the SC: a) to possess a unique identity; and b) to “hold”or “house” a plurality of SC components by relating the SC componentsusing the unique identifier.

The SCR components (e.g., the SC component; the SCC component; the SCChost entity component; and the object component) described above areintended to be interoperable with many different types of softwaresystems. This allows for information, in the form of structured and/orunstructured data, to be captured and maintained as an object traversinga sequential chain changes its profile in terms of ownership, location,physical and/or chemical characterization or of other nature of change.Generally, different owners incorporate different software and databasesthat often cannot effectively communicate with one another. Because ofthis, information related to an object's transit through and processingwithin a sequential chain may be lost as the object changes ownershipand/or position while transiting a sequential chain. The SCR componentsdescribed herein are designed to be software/database independent,allowing for the sharing of data across disparate systems. Additionally,the SCR components described herein may be operable with various formsof analytics software. For example, the components described herein maybe used with data mining software, statistical analysis software, etc.to allow analytical processing of an object and its related data. Whilea specific taxonomy is used to describe certain aspects of the SCRcomponents disclosed herein, one of skill in the art will appreciatethat the taxonomy is provided for ease of illustration and is in no wayintended to limit the scope of usage for the SCR components disclosedherein.

A plurality of computations may be performed on data received by adatabase that is designed as part of an embodiment of the SCR. By way ofexample but not limitation, an embodiment of the SCR may employrelational database functionality to create data sets from a pluralityof individual data objects. Alternatively, other types of databasestructures may be used.

Sequential Chains

FIG. 1 is a flowchart illustrating an embodiment of a method by which auser may commence the construction of an embodiment of the SCR systemand method. A system facilitator 102, a system user 104, or another maybegin specification of a particular embodiment by selecting a scope ofthe embodiment 106. By way of example but not limitation, one embodimentas described herein is an embodiment of SCR for the oil and gasindustry, wherein such embodiment, more generally, herein is referred toas the ‘object-centric’ embodiment. Alternatively, other embodiments ofSCR may be selected, as such other embodiments herein are described andillustrated. Once an embodiment's scope is determined 106, the systemfacilitator 102, a system user 104, or another—for instance, a databasesystem designer or other appropriate information technologyprofessional—may select the particular database technology 108 judged tobe most suitable to the particular scope of embodiment targeted for theSCR system and method. By way of example but not limitation, relationaldatabase technology may be selected as an appropriate technology aroundwhich to design an embodiment of the SCR. As used herein, the term RDBMSsignifies a relational database management system, such as offered bysoftware vendors Oracle®, IBM®, Microsoft®, and other enterprises.

Embodiments described herein use RDBMS software as a component of theSCR system and method. Hereafter in this description, examples shown forembodiments of the SCR system and method are derived by using an RDBMSsoftware application offered by Microsoft®—Microsoft® Office Access™2007. As will be apparent to an artisan of ordinary skill, otherdatabase software and/or other forms of database technology other thanrelational database technology may also be selected for use in designingand operating an embodiment of the SCR. Likewise, RDBMSs other thanthose vended by Microsoft® may also be employed. After selecting anappropriate database technology 108, a system designer defines aplurality of entities, or relations, which may be used in an SCRembodiment 146, as described next.

A system designer or another, with or without collaboration with systemusers 104, may define a plurality of database entities 146, which arealso referred to herein as database relations. As used herein in adatabase context, the term entity or relation means something (e.g., anobject) that a system designer or user can identify and wants to keeptrack of. As shown in FIG. 1, by way of example but not limitation,entities may be: enterprises; users; objects; sequential chains; SCcomponents; SCC host entities; and other entities. Such definitions ofentities by a system user or another may be declared into, and receivedby, a database.

FIG. 2 is an illustration depicting embodiments of database entities andrelationships. Such entity data and entity relationships may be created,managed, and maintained by the various SCR systems and methods disclosedherein. By way of example but not limitation, element 202 depicts adatabase representation, as provided by exemplary database software, forthe enterprise entity. The enterprise entity 202 is received into an SCRdatabase 220 as a result of a system designer or another declaring itinto the database via a suitable database software system such as theexemplary database software 222. In the instance of the enterpriseentity 202, a plurality (t)-count of data attributes pertaining to theenterprise entity is created as a result of the process of declaringattributes into, and receiving them by, the database 220. Similarly,FIG. 2 depicts other exemplary entities and their associated dataattributes received into the SCR database for entities: user 204; object(or item or product, etc.) 206; sequential chain 208; SC component 210;and SC component host entity 212.

Definition of entity relationships may be performed by a user, by theSCR system, or by any other process, following the earlier definition ofa plurality of entities. As used herein, the term entity relationshiprefers to an association, made within a database, among entity classes.FIG. 3 shows example embodiments of entity relationships amongst threeexemplary entities 208, 210, 212. For instance, two entity relationships302, 304 are shown between the exemplary entity sequential chain 208 andthe exemplary entity SC component 210. Respectively, the two entityrelationships are indicated in FIG. 3 to be created by using asequential chain's unique ID reference 302, e.g., a form of identifier,and the sequential chain's name 304 as the common data attributes forthe two exemplary entities. In an analogous manner, two other entityrelationships 306, 308 are shown between the exemplary entity SCcomponent 210 and the exemplary entity SC component host 212.Respectively, the latter two entity relationships use a SC componenthost's unique ID reference 306 and the SC component host's name 308 asthe common data attributes for these two entity relationships. Inembodiments, an SCR database receives declarations of entityrelationships from a system designer, system facilitator, user, oranother, via database software.

Having described example embodiments of different types of data andrelationships that may be managed and maintained by the various SCRsystems and methods, FIG. 4 provides an example embodiment of asequential chain (SC) that may be represented using the componentsdescribed herein. FIG. 4 is an embodiment of a block diagramillustrating a conceptual view of the construction of an exemplarysequential chain 800, comprised of SC components 802, 804, 806, 808,810, representing (n)-count of SC components. A system designer oranother may declare a particular instance of an entity relationship(e.g., a logical relationship between two particular entities) viadatabase software, thereby enabling a database in an embodiment toreceive data describing an intended entity relationship. By way ofexample but not limitation and referring FIG. 4, a particular instanceof a sequential chain, as conceptually shown in element 800, may bedeclared into, and received within, a database, via database software byusing the entity classes for sequential chain 800 and SC component 802to create relationship instances that describe a plurality of particularSC components comprising a particular sequential chain.

For the embodiment shown in FIG. 4, specification by a user or anotherof a particular sequential chain 800 is received into a database,whereby the sequential chain is comprised of (n)-count of particular SCcomponents 802 through 810. As shown in FIG. 4, the sequential chain andthe SC components comprising it may each be uniquely identified viaparticular identifiers (e.g., by use of non-repeating, sequential wholenumbers as a form of identifier) and also may be assigned a plurality ofother attributes, including attributes such as a name, an enterpriseowner, an SC component rank and other attributes. Thus, in theforegoing, have been described four elements of a database system thatmay be used to describe even large, complex sequential chain systems.The four elements may include: entities, attributes, identifiers andrelationships. Embodiments of the SCR system and method described hereinmay employ these four (and other) database elements.

In FIG. 4, a particular embodiment of SCR is shown to classify SCcomponents (or SCCs, which comprise sequential chains) into two types ofcomponents, e.g., process activities (or PAs) as designated by therectangles 802, 806, 810 and change of control actions (or CCAs) asdesignated by the triangles 804, 808. By way of example but notlimitation, a process activity may be a set of oil producing wells or apetroleum refinery. A change of control action may be an oil tanker ornatural gas pipeline, either of which, for instance, would transportcrude oil or natural gas from one process facility to another. Aconnotation of temporal and/or spatial movement by the term, ‘change ofcontrol’—e.g., in reference to change of control actions, or CCAs, asone form of SC component—may be convenient to system designers or toothers who construct a particular embodiment; however, terms other thanPA and CCA may also be used in other embodiments.

The use of PAs and CCAs allows for the use of logical checks to ensurethat a SC is validly constructed and complete. For instance, an SCembodiment herein provides for (n)-count of sequential chain components(SCCs) as comprising a sequential chain, wherein (n) is any odd wholenumber such as, e.g., 5, 7, or 15. This example taxonomy also providesfor sequential chains to commence and end with a process activity, or PA[signified by the rectangles 802, 810 in FIG. 4] and for change ofcontrol actions, or CCAs [signified by the triangles 804, 808 in FIG. 4]to be inserted between each two neighboring process activities. Thus,one exemplary, but non-limiting, schema provides for each neighboringpair of PAs to be linked by one change of control action (or CCA) andfor a sequential chain to commence and end with a particular processactivity. Alternatively, other schema may be used in a particular SCRembodiment.

A particular embodiment of the SCR system and method may be constructedto include suitable logic tests to ensure that the intended structure ofall sequential chains is accomplished in reification. For instance, asuitable logic test may be created to ensure that: (i) an SCR database[e.g., shown as element 220 in FIG. 2] receives declared data pertainingto a number of discrete process activities (or PAs) equal to [(n+1)/2]and to a number of discrete change of control actions (or CCAs) equal to[(n−1)/2] for any particular sequential chain, wherein (n) represents anodd whole number; and (ii) the sequential chain commences with an SCcomponent that is a process activity, or PA [thereby, ensuring that aprocess activity also exists at the end of the sequential chain,assuming (n) is an odd whole number]. In another embodiment, other ordifferent logic tests may be employed with the embodiments disclosedherein. For example, a test may be included to ensure that no unique SCcomponent appears more than once in a declared sequential chain (unless,for instance, some form of re-circulation of objects through aparticular SC component is intended by a system designer or another).

One of skill in the art will appreciate that the embodiments describedherein may be employed in, or for, various different sequential chainsrelated to various different industries. As such, the rules for each SCmay vary depending upon the needs of the particular industry or thenature of sequential chain applicable to the particular industry. Anynumber of logic tests may be employed with the embodiments disclosedherein to ensure that the SC conforms to and accurately represents aspecific sequence of events, processes, steps or the like. Thus, forreasons of data control and data quality, it may be appropriate for aparticular embodiment of the SCR system and method to include aplurality of logic tests to ensure both data accuracy and sound logicalrelationships of the data elements received into, and accessed from, aparticular SCR database system. Employment of a particular taxonomy andschema for forming and declaring sequential chains, such as describedherein, enables the construction of such logic tests. As will beapparent to an artisan of ordinary skill in database design, a pluralityof other taxonomies and other logic tests may be constructed, dependingon the nature and complexity of a particular application environment fora particular SCR embodiment. The extent and complexity of such taxonomyand logic tests may also reflect the extent of data quality control thatis intended for a particular SCR embodiment, as well as the data qualitycontrol that is available within the application space pertaining tosuch particular SCR embodiment.

Next are described aspects of SCR's data and logical structures thatenable data relation, or association, amongst a plurality of data,including, but not with limitation, data pertaining, respectively, toobjects (e.g., products) in sequential chains, sequential chains, SCcomponents comprising a sequential chain, and host entities hosting SCcomponents, for objects as they exist, or may exist, in a particular SCcomponent within a particular sequential chain.

FIG. 5 is a block diagram depicting embodiments of relationships amongsta sequential chain component 500; a host entity 504 that hosts the SCcomponent; an object 508 that exists in the SC component; and a document512 that contains data pertaining to the object as the object existsrelative to the SC component. Each of these elements represents adatabase entity that may be received by an SCR database pursuant to thedata communication procedures as will be described later. The linesconnecting these entities in FIG. 5 [for instance, the line connectingthe entity SC component 500 and the entity object 508] signify an entityrelationship, which also may be received (e.g., as a specification of auser or another) by an SCR database.

Each of database entities 500, 504, 508, 512 may have data associatedwith it pertaining, respectively, to: SC component data 502, SCcomponent host entity data 506 (also referred to as ‘host milieu data’),object data 510, and document-related data 514. The document entity 512and corresponding document data 514 may be applicable when an SCRembodiment is designed and operated for an environment involvinguncovered objects; the document entity may also be employed in anenvironment involving covered objects or a hybrid environment involvingboth covered and uncovered objects. As herein later described, thedocument entity 512 may provide a particular functionality, relative touncovered objects, whereby a DocString identifier may be formed to giveobject unique identity to uncovered objects, which objects otherwise maybe incapable of consistently holding an existing form of object uniqueidentifier. Pursuant to the principles of Boolean logic (also referredto as Boolean algebra), an SCR database enables data associations orrelations amongst a SC component 500 and the database entities relatedto the SC component, that is, to: a SC component host entity 504; anobject 508 that exists in the SC component; and a document 512 thatpertains to the object and to the SC component. In embodiments, data502, 506, 510, 514 pertaining to these four entities may be received byan SCR database via appropriate data forms.

In the embodiments described herein, a portion of a data structure bywhich an SCR database enables association, or relation, of a pluralityof data 502, 506, 510, 514 [which data pertains to an object 508 thatexists, or has existed or may exist, in a particular SC component 500; ahost entity 504 in which the SC component exists; and a document 512]may be used in forming a DocString identifier, which is herein belowfurther described. A data structure employed in the SCR system andmethod enables the association, therefore, of data for an object, a SCcomponent, and a SC component host entity and also for data pertainingto a document entity 512 when the document entity is employed in aparticular embodiment. As used herein, the term vertical logicalconjunction signifies data associations, or relations, for datapertaining to an object in a particular SC component. The entity SCcomponent 500 enables conjunction of data attributes and data valuespertaining to the other entities linked to it in the four-entity networkshown in FIG. 5. Next is described the manner in which a data set formedwithin an SCR database, as just described for a particular SC componentin a sequential chain, is associated with other data sets similarlyformed for all SC components that comprise a sequential chain. Asdescribed above, registering a SC in a registry provides the SC with aunique identifier that may be used to associate all of the data (e.g.,data for SC components, SC component hosts, objects, etc.) related tothe sequential chain.

The particular embodiments provided herein illustrate the manner inwhich vertical logical conjunction enables an SCR database to create adata set that associates particular data pertaining to an object that isrelated to a particular SC component, which component may comprise partof a sequential chain. FIG. 6 and the following description illustratethe manner in which, in embodiments, a group, or set, of a plurality ofsuch SC component-specific data sets may be formed, thereby relatingdata in each particular data set (e.g., data pertaining to a particularSC component and a particular object in that SC component) to other datain all other such data sets for all SC components in which an object mayexist or has existed in a uniquely identified sequential chain. As usedherein, the process of associating a larger set of data sets so formedfor a plurality of SC components (through which an object transits, ormay transit, within a particular sequential chain) signifies horizontallogical conjunction.

As shown in FIG. 6, a data set 600 may be formed in an SCR database fora particular SC component. Data set 600 may pertain to an object 508that exists, or has existed, in a particular SC component 500.Represented in the bottom portion of FIG. 6 is a time-sequential set ofuniquely identified SC components (in adjacent rectangles), togethercomprising a uniquely identified sequential chain, wherein each discreteSC component, from component 1 to component (n), is shown in a series oftime jumps from time T₍₁₎ 602 to time T_((t)) 604. Each time (t)represents a discrete time or time interval during which an objectexists in, or has existed in, the SC component that relates to time (t).Such discrete time or time interval may be referred to as a timestamp,which term is used herein.

In embodiments, data relative to a time or time period, defined byparticular timestamp(s), may be received by and stored in an SCRdatabase as an attribute of: an object, e.g., a product; a SC componenthosting the object during the time referenced by the timestamp(s); adocument describing the object and/or the SC component; all three ofthese entities; or otherwise. In FIG. 6, the large arrow 608 extendingbetween the data set 600 for SC component_((n)) and the set of timejumps through (n)-count of SC components represents the movement throughtime in which the object 508 transits through a sequential chain,wherein the sequential chain is comprised of the ordered sequence of SCcomponents, that is, SCC₍₁₎ through SCC_((n)), and wherein thesequential chain is given its own unique identity which is received byand stored in the SCR database via a data entry form or any other methodof gathering and storing data known to the art. The reference herein to“sequential chain registry system and method” employs the term“sequential” from this notion, or construct, of a SC component-centereddata set, acting as a hub, that accretes over time into a larger dataset as an object sequentially (in time) moves within a uniquelyidentified sequential chain through a plurality of uniquely identifiedSC components comprising the sequential chain.

FIG. 7 is a block diagram illustrating an embodiment of a data set thatmay be organized and compiled or received within an SCR database for aparticular object that transits a sequential chain. Such extended dataset for an object 508 is comprised of all data sets for each particularSC component that comprises a uniquely identified sequential chain andin which an object exists or has existed. As previously described, anobject being tracked through a sequential chain may be dynamic. That isan object may change form as it traverses the sequential chain. Asdescribed herein, an object may change position (e.g., transit throughspace and time) as well as change its physical, chemical or other natureof form. The SCR embodiments described herein are able to capture thesechanges while maintaining data related to the object as it traverses thesequential chain. The use of the unique identifier assigned to aregistered SC allows capturing data related to the object despite theobject's undergoing dynamic changes.

In embodiments, data may be received by an SCR database such that dataset 600, shown in FIG. 7, is compiled or received in the SCR databasewith respect to an object 508 that exists or has existed in SC component500 for the time or time interval relating to timestamp T₍₁₎ (702). Aplurality of such SC component-specific data sets may be received in theSCR database for each particular uniquely identified SC component in auniquely identified sequential chain through and including the finalsuch data set 706, which pertains to the final SC component in thesequential chain and to timestamp T_((n)) 704. By receiving suchcomplete data set within the indicated data structure, an SCR databaseis enabled to: store all received data in relational tables; manipulatesuch data in a plurality of manners in response to users' data queries;and return such manipulated data to users in response to such queriesvia a data communications network. With an SCR database so enabled,users, enterprises and others may obtain significant informational valuerelating to objects (such as products) that are brought into markets viasequential chains and also relating to the components comprisingsequential chains, to the host entities hosting such components, and toother information assembled or compiled via an SCR embodiment.

Data received by an SCR database may be declared by one or a pluralityof system users. For instance, a single user may declare, via data entryforms, all data into the SCR database for a particular object as ittransits all SC components comprising a uniquely identified sequentialchain. Alternatively, data received by the SCR database may be declaredby one user with respect to one or more SC components, while data may bedeclared by different users with respect to other SC components. By wayof example but not limitation, an SCR database may receive data, viadata entry forms: from a field administrative staff person for one ormore upstream facilities (as SC components) and from a corporate financestaff person for other downstream operations (also as SC components). Asused herein, “users” may also include natural persons, computerapplications and other processes. For example, the SCR database mayreceive data from other sequential chains or sequential-chain systems.This can be particularly useful in situations where data relative to asequential chain is currently stored in separate siloed database systemsthat are controlled by different organizations. The SCR registry permitssuch siloed information to be received and correlated according toformats that accommodate inter-organizational sequential chains. Forexample, the SCR registry enables data integration across various,siloed enterprise systems (e.g., Oracle vs. IBM databases) which allowsfor the continued tracking of data related to an object as it changesownership and moves through different information systems.

Further, an SCR database may receive data from enterprise system userswherein such data relates to: an object that transits a sequentialchain; a sequential chain that hosts a plurality of SC components; aplurality of SC components, which comprise a sequential chain; and some,but not necessarily all, of the data attributes pertaining to a SCcomponent host entity. An example of an SC component host entityreceived by an SCR database may be, for instance, the classification(such as ‘country’) of a host entity of a particular SC component, as adata attribute, and the particular name of such host entity (such as‘Algeria’) as a data value for such data attribute. Insofar as many dataattributes relating to an SC component host entity, which hosts aparticular SC component, may be specific to the host entity and not toan object or to other nature of database entities, an SCR database mayreceive data from a system facilitator for data attributes that describea particular host entity. In such manner, a system facilitator may (butneed not) be one who is outside of the particular entity managing an SCRsystem implementation, whereby such system facilitator may focus on datathat pertains to SC component host entities, apart from an enterprise'sobjects that may exist in SC components hosted by such SCC hostentities.

In embodiments, an SCR database may receive data from a plurality ofdifferent sources within an application environment of a particular SCRembodiment. Enterprise data (e.g., data comprising the type of datastored by one of the SCR data types disclosed herein) may be received byan SCR database from enterprise users and enterprise customers, whiledata describing a SC component host entity may be received by an SCRdatabase from a system facilitator who focuses on providing hostentity-specific data. For example, in embodiments SCC host entity datamay be centrally maintained in a central repository. Because SCC hostentity data may be relatively static in time (e.g., as may be contrastedto object data), central management of such SCC host entity data makesit easier to provide users with the proper SCC host entity data ratherthan requiring the user to discover that information herself. Managingthe data as such allows for SCR system users a scale advantage by havinga neutral party or parties maintain SCC host entity data which may bedata attributes that are generated by many entities such as the UN, IMF,etc. pertaining to characteristics of countries. For example, the UNmaintains a ‘human development index’ (HDI), which is updated annually;Columbia University maintains a number of country-specific environmentalindicators; Transparency International maintains an annually updatedindex of Corruption Perceptions Index (CPI), etc. By providing a centralrepository for SCC host entity data, users do not have to individuallymaintain such data.

Blend Platform

FIG. 8 is a block diagram illustrating an embodiment of a sequentialchain construction of a particular class of SC component (e.g. SCcomponent (q) 826) with functionality of a blend platform. As usedherein, the functionality of a blend platform is that which enables oneor more uniquely identified objects [e.g. object (a) 822] to becombined, or blended, with one or more other uniquely identified objects[e.g. object (b) 824], wherein such objects' unique identity andexistence within a uniquely identified sequential chain (and theconstituent SC components comprising the sequential chain) have beenrecorded as data received by and stored in an SCR database and, further,whereby a combined, or blended, object [e.g. object (c) 816] may becomea distinct object that may be further associated with one or a pluralityof additional SC components (e.g. SC component (r) 830) that aresituated downstream of the blend platform 826. An exemplary instance ofthe functionality of a blend platform 826 is described below.Additionally, values of data attributes for object (c) 828 may beseparately measured or otherwise determined after the object (c) hasbeen formed, or blended, in the blend platform. In this latter instance,once such values are measured or otherwise determined, an SCR databasemay receive data for such values via means described earlier.

In embodiments, an SCR database may receive data pertaining to: anobject (a) 822; a sequential chain 800; and (n)-count of SC components802, 804, 806, 808, 810 comprising such sequential chain, wherein suchdata may include data values for a plurality of data attributes,including a data attribute for one or more forms of unique identifiers,which give unique identity to data objects representing all of suchobject, sequential chain, and SC components (and, additionally, SCC hostentities). In a similar manner, an SCR database may receive datapertaining to: an object (b) 824; a sequential chain 801; and (p)-countof SC components 812, 814, 816, 818, 820 comprising such sequentialchain, wherein such data may include data values for a plurality of dataattributes, including a data attribute for one or more forms of uniqueidentifiers, which give unique identity to data objects representing allof such object, sequential chain, and SC components (and, additionally,SCC host entities). For clarity, it is noted that an SCR database, inaddition to receiving such data, also may receive data (via a data entryform) that associate the respective object—that is, object (a) 822 andobject (b) 824—with each SC component in which such object exists andfurther which associate each uniquely identified SC component with theuniquely identified sequential chain that hosts each SC component andSCC host entity.

SC component (q) 826, as an SCR blend platform, may receive object (a)822 and object (b) 824, thereby resulting in formation of object (c)828. In embodiments, object (c) 828 may be assigned its own uniqueidentifier or DocString Identifier. As will be apparent to one ofordinary skill in the art, two or more such objects may be conjoined inblend platform 826, but, for clarity of representation, only two suchobjects are described herein and with FIG. 8. The combined, or blended,object (c) 828 may terminate its transit of a sequential chain at theblend platform, e.g. at the SC component (q) 826, or alternatively, suchblended object may continue its transit to a further downstream SCcomponent (r) 830. In embodiments, the SC component (q) 826 may also bea component of SC 800, SC 801, or both.

The references above to an object transiting a sequential chain andcombining with another object in a blend platform, and including thepossible further transit of the blended object to other SC components,signify an SCR database receiving data, via means herein earlierdescribed, pertaining to the objects, the sequential chains and SCcomponents comprising the sequential chains, and to any SCC hostentities associated with SCCs. Referring to FIG. 18, computed values ofdata attributes for a blended object, as such blended object is hereinabove described, may be obtained by data manipulation in a plurality ofmanners, including computation: within an SCR database 220; within adata analysis module 1810; outside of the SCR database and the dataanalysis module, with resultant computed data received by the SCRdatabase via means as herein earlier described; via some combination ofthese first three manners; or otherwise.

In embodiments, a blend platform 826 may be either a process activity,or PA, as indicated by the rectangle 826 in FIG. 8, or a change ofcontrol action, or CCA. Similarly, the SC component 814, if any, intowhich a blended object (c) 828 transits, may also be either a PA or aCCA. Further, in embodiments, if blend platform 826 is: i) a PA, thenthe succeeding SC component 830, if any, will be a CCA; ii) is a CCA,then the succeeding SC component 830, if any, will be a PA. In suchmanner, the previously described taxonomy and data structure arepreserved for creating sequential chains (as database entities) from SCcomponents (also as database entities), whereby a sequential chaincommences and ends with a PA and with a CCA linking each adjoining PA.As will be apparent to an artisan of ordinary skill and as earlierherein described, other nature of taxonomy and data structure may beused. The taxonomy as herein described is one of various particularmethods by which users may create logic tests to ensure clear andconsistent construction of embodiments of sequential chains from SCcomponents. System designers, users and others may choose to articulatealternative forms of taxonomies.

By way of example but not limitation, the following description is givento illustrate manipulation of data pertaining to objects being combined,or blended, at a SC component functioning as a blend platform in aparticular embodiment of the SCR system and method. Object (a) 822 andobject (b) 824 may be, for instance, two distinct lot quantities ofcrude oil, say, of 50,000 tons each. These two objects may be combined,or blended, at SC component (q) 826, each such object having exited itsrespective prior SC component (n) 810 or SC component (p) 820. Object(c) 828 may be created within the blend platform, e.g. within SCcomponent (q) 826, resulting in the object (c) being a new lot quantityof 100,000 tons of blended crude oil. For instance, the blend platform,e.g., SC component (q) 826, may be a large steel storage tank located atthe premises of a petroleum refinery and used for storing crude oil andcrude oil blends. In turn, SC component (n) 810 and SC component (p) 820may each be a particular crude oil pipeline system that transports crudeoil to the refinery storage tank.

The combined, or blended, object (c) 828 has associated with it aplurality of data attributes and corresponding data values. Inembodiments, data values for these attributes of object (c) 828 may becomputed via a plurality of methods. For instance, for the attribute‘quantity,’ the quantity of crude oil associated with the object (c) maybe computed within an SCR database, resulting in a data value of 100,000tons for the blended object (c) 828. Another example of computed data,whereby a blended data attribute value may be computed for the blendedobject from data relating to objects comprising such blended object,follows. A crude oil blend of two different types of crude oil (forexample, 50,000 tons each of Arabian Light and West Texas Intermediatecrude oils) may have a combined, blended value of 9.7 for the attributeof the Corruption Perceptions Index, or CPI, as published by theTransparency International (TI) organization. Such exemplary blendeddata attribute may be computed from the CPI values as these are publiclyreported by TI. Data values may be so computed for a plurality of dataattributes for blended object (c) 828.

For these two exemplary instances of a blended object being formed fromtwo distinct crude oil lots, it may be that a plurality of dataattributes are not amenable to simple linear computation, such asillustrated above for the combining of quantities of the separate lotsof an object. Accordingly, in such circumstance, a system designer oranother may include appropriate computational modules: within an SCRdatabase; within a data analysis module; or otherwise; and whereby suchcomputational modules may perform computations of varying complexity inorder to obtain data values for particular data attributes of theblended object. Such computational modules—for instance, productsoffered by SAS Institute, Inc. of Cary, N.C. or a variety of spreadsheetapplications—therefore, may be employed to manipulate data to obtainvalues for data attributes pertaining to a combined, or blended, objectformed in a blend module (also herein referred to as a blend platform).For instances in which computed data values pertaining to dataattributes of a blended object are obtained via computation outside ofan SCR database, such data values and data attributes may be received bythe SCR database in the manner herein earlier described.

Split Platform

In further embodiments, in addition to blending multiple objects into anew blended object, an object may be split into multiple differentobjects. The SCR systems and methods disclosed herein are capable oftracking each split object through a sequential chain. FIG. 9 is a blockdiagram illustrating an embodiment of a conceptual construction by asystem designer or another of a particular class of SC component [e.g.SC component (t) 902] with functionality of a split platform. As hereinused, the functionality of a split platform is that which enables anobject [e.g. object (c) 828] to be separated in a manner, e.g. to besplit apart, at the split platform such that two or more componentobjects [object (a) 822 and object (b) 824] are derived, wherein suchpre-split object's [e.g. object (c) 828] unique identity and existencewithin a uniquely identified sequential chain [that is, within asequential chain that includes the uniquely identified SC component (t)902 as a split platform] have been recorded as data received by andstored in an SCR database and, further, whereby the disaggregated, orsplit-apart, objects [e.g. object (a) 822 and object (b) 824] may be orbecome distinct objects that may be further associated in the databasewith other sequential chains, for instance, with sequential chain 800 orsequential chain 801.

For example, as illustrated in the embodiment depicted in FIG. 9, anobject (c) 828 may transit into a split platform [e.g., SC component (t)902] and be split apart in a manner that creates object (a) 822 andobject (b) 824. Alternatively, more than two such split-apart objectsmay be formed at a split platform. The split-apart objects may theneither: cease their transit of a sequential chain; or advance furtherdownstream to another sequential chain such as sequential chain 800 orsequential chain 801. As will be discussed further with respect to FIG.11, a sequential chain may contain several smaller sequential chains,each of which may, itself, comprise a proprietary sequential chain.

Data values for particular data attributes pertaining to the split-apartobjects may be computationally derived in the manners herein abovedescribed for a blend platform. Alternatively, such data values for thesplit-apart objects may be separately measured or otherwise determined,following which an SCR database may receive such data values for thedata attributes pertaining to the respective split-apart objects viameans herein earlier described. An exemplary instance of thefunctionality of a split platform 902 is described next.

SC component (t) 902, as a split platform, may be a crude oildistillation tower in a petroleum refinery. Object (c) 828 may be aquantity, e.g., as a continuous flow, of crude oil, which is chargedinto the crude oil distillation tower. A plurality of distilled andresidual hydrocarbon materials—such as represented by object (a) 822 andobject (b) 824—may be formed by operation of the crude oil distillationtower. Such split-apart objects may be, for instance, olefins and othergases, light oils, and residual heavy oils, all of which may be formedvia a crude oil distillation process. Thus, in such manner, the SCcomponent (t) 902 is shown to function as a split platform.

As will be apparent to one of ordinary skill in the art, an SCcomponent—such as SC component (q) 826 in FIG. 8, operating as a blendplatform, or SC component (t) 902 in FIG. 9, operating as a splitplatform—may also operate in a manner that combines the respectivefunctionality of both a blend platform and a split platform. FIG. 10 isa block diagram illustrating an embodiment of such dual functionality ofa SC component.

Two or more objects—for instance, (m)-count of objects representedcollectively by object (1) 1002 and object (m) 1004 in FIG. 10—maytransit as separate feedstocks within uniquely identified sequentialchains into SC component (w) 1010, which, first, functions as a blendplatform. With such blend-platform functionality, as herein abovedescribed, these feedstocks may be blended into a single, compositeobject. Following such blending functionality, the SC component (w) 1010may next function as a split-platform, thereby creating one or aplurality of split objects—for instance, (x minus n plus 1)-count ofobjects represented by object (n) 1006 and object (x) 1008. Objectsexiting SC component (w) 1010 may proceed further downstream to otheruniquely identified SC components or may cease their transit of uniquelyidentified sequential chains and SC components. In embodiments, certainattributes of the objects (1) 1002 and (m) 1004 may be calculated uponthe blending described above and then distributed to the separatedobjects created by the subsequent splitting into the objects (n) 1006and (x) 1008. For example, if a purity attribute for the feedstock(e.g., the sulfur or metals content of the feedstock) was recalculatedupon the blending of objects (1) 1002 and (m) 1004 (each of which mayhave had separate and distinct purity attributes prior to blending),that purity may be assumed, in embodiments, to be applicable to bothobjects (n) 1006 and (x) 1008 after splitting. By way of example but notlimitation, object (1) 1002 may represent a quantity of diesel fuel asmay be refined from crude oil within process units of a petroleumrefinery; object (m) 1004 may be a quantity of additive such as coloreddye used in marking (e.g. for taxation purposes) certain grades orclasses of diesel fuel; and object (x) 1008 may represent thecolor-marked diesel fuel emanating from the blend platform (w) 1010.Upon knowing the respective volumes (or weights) of objects (1) 1002 and(m) 1004, one may compute the concentration of object (m) 1004 containedin object (x) 1008, which latter object may be comprised of the combinedquantities of objects (1) 1002 and (m) 1004.

Data attributes and data values for both in-bound and out-bound objects,which transit through a SC component (w) 1010 operating in the dual(blend- plus split-) platform mode, as just described, may be receivedby an SCR database via the means herein described.

Modification Platforms

Modification platforms may be used to represent changes to an object asit traverses a sequential chain. As will be apparent to an one ofordinary skill in the art, in embodiments a modification platformfunctioning in a dual mode, e.g. as both a blend- and a split-platform,alternatively, may be designed as more than one modification platform.For instance, the dual functionality described above for SC component(w) 1010, shown in FIG. 10, alternatively, may be represented by one SCcomponent functioning as a blend platform and another SC componentfunctioning as a split platform in lieu of a single SC componentfunctioning as a dual (blend-plus-split) platform. The text herein aboveand FIGS. 8, 9, and 10 have described and illustrated, respectively, SCcomponents that operate: with functionality of a blend platform, wherebyobjects are combined or blended; with functionality of a split platform,whereby an object is split apart into a plurality of component objects;and with a dual functionality, whereby a plurality of objects may firstbe blended and, subsequently, split into a plurality of other objects.As will be apparent to an artisan of ordinary skill, other definitionsof such platform functionality may also be employed in a schema designof a particular SCR database. For instance, the dual functionality justdescribed—whereby an SC component first blends objects and thenseparates a blended object into other, split objects—may be reversedsuch that an SC component first operates in the split-platform mode andthen in the blend-platform mode. An example of the latter may comprise apetroleum refining process, whereby a crude oil stream is firstfractionated, thereby producing several product fractions; and, then,whereby a particular product fraction is combined with certainadditives, thus resulting in an additive-enhanced product derived fromthe pre-fraction raw material stream plus the additive.

In addition to SC component functionalities of a blend platform and asplit platform, described herein above and with FIGS. 8, 9, and 10, theSCR system and method may also employ another form of SC component in anembodiment utilizing a change platform. As herein used, thefunctionality of a change platform is that which enables an object to bechanged in any manner other than by blending of two or more objects (aswith blend platform) or by splitting apart an object (as with splitplatform). As herein used, therefore, the exemplary taxonomy of the SCRsystem and method employs three types of modification platform: blendplatform, split platform, and change platform.

SC components functioning (within an SCR embodiment) as either a blendplatform or a split platform, as herein above described, may effectphysical changes to an object as the object progresses in a sequentialchain. For instance, the combination of two feedstock streams within anSC component functioning as a blend platform may entail only physicalchanges, such as creating one larger object from two smaller objects.Another such instance is the physical change entailed with theliquefaction of natural gas into a liquid state in a liquefactionfacility, thus representing a physical phase change in the object'snature.

By contrast, an SC component functioning as a change platform mayoperate in a manner to cause chemical or other nature of changes in, orto, objects. Thus, referring to FIG. 9, for instance, an object (c) 828may be subjected to chemical processes or reactions in SC component (t)902, such that derivative objects (a) 822, (b) 824 are created. By wayof further example but not limitation, a change platform may treat witha change of ownership of an object, such as occurs when an object isbought and sold within an SC component. Another example of a change thatmay occur in a change platform is the payment of customs duties withinthe platform such that an attribute “price” may be modified to become“price including customs duties.”

As will be apparent to an artisan of ordinary skill, SC componentmodification platforms—such as the blend, split and change platformsdescribed herein—are system-design architecture conveniences that may beemployed in the construction of an SCR database within a particularembodiment of the SCR system and method. Other SC componentfunctionalities may also be defined and designed into the architectureand taxonomy of a particular SCR embodiment. Similarly, the schemaillustrated in FIG. 4 and herein above described, is another such systemarchitectural convenience. Uniquely identified SC components, aselemental segments that may comprise a uniquely identified sequentialchain, may be employed in a plurality of manners as suited to aparticular embodiment of the SCR system and method.

A sequential chain (as a database element) may be designed as an elementreceived by, and stored in, an SCR database in a manner whereby one or aplurality of SC components comprising the sequential chain—and includingSC components functioning as a blend platform, a split platform, achange platform, or other nature of such platforms—may host a particularobject (and including changed forms of the object) at more than a singleparticular time or time interval. For instance, sequential chains mayinclude functionality for recycling of objects, such as the return ofscrap steel to a steel re-processing and fabrication facility. Thus,embodiments of the SCR system and method may employ a schema wherebysequential chains may be articulated within an SCR database in a linearfashion with objects transiting the sequential chain in a particularsequential order. Alternatively, other embodiments of the SCR system andmethod may employ a data schema whereby objects transit a sequentialchain in a non-linear manner, for instance, when object-recycling withina sequential chain occurs.

As herein earlier described, an embodiment of the SCR system and methodmay be constructed wherein an SCR database may receive data pursuant toa particular schema and taxonomy such that a particular sequential chainand its constituent SC components, as elements in the sequential chain,may be uniquely identified and related within the database. Also asdescribed earlier, the schema and taxonomy applied in a particular SCRembodiment may be other than those used herein. Such schema and taxonomymay be tailored to a particular application environment in which an SCRembodiment is implemented.

By employing a suitable schema and taxonomy within the architecture of aparticular embodiment, a system designer or another enables the SCRsystem and method not only to associate data attributes and data valuesamongst uniquely identified sequential chains as database elements (e.g.data type-2) and uniquely identified SC components as database elements(e.g. data type-3) comprising sequential chains, but also enables thosedata to be further associated with: uniquely identified host entities(e.g. data type-4) that host SC components; uniquely identified objects(e.g. data type-1) that exist in, transit through, and may be modifiedwithin the SC components of a sequential chain; and other data. The SCRsystem and method enables such multi-factor data associations, orrelations, amongst all the data types, or categories, just described andto enable manipulation of such data in response to search queries suchthat multi-dimensional data and information may be returned by SCR tosystem users and to others. Such multi-dimensional data and information,in some instances, is what is commonly referred to as instances ofbusiness intelligence, or BI.

Mixed Sequential Chains

FIG. 11 is a block diagram illustrating another feature of a data schemathat may be employed in an SCR embodiment. This particular schema is astructure whereby an SCR database is enabled to receive data objectsthat describe a uniquely identified sequential chain ‘C’ 1112 that iscomprised of two or more other uniquely identified sequential chains ‘A’1102 and ‘B’ 1134, which are joined by an SC component 1110 functioningas a change of control action, or CCA. As herein used: sequential chains‘A’ and ‘B’ 1102, 1134 are referred to as proprietary sequential chains(or PSCs); sequential chain ‘C’ 1112, as a mixed sequential chain (MSC),that is, a sequential chain comprised of the three elements 1102, 1134,1110; and SC component 1110, as a linking change of control action, orlinking CCA. Also as used herein, for convenience: process activity isreferred to as PA; change of control action, as CCA; and linking changeof control action, as linking CCA. Alternatively, other data schema andtaxonomies may be employed in order to link, or chain together,previously formed sequential chains. Such linking or chaining togetherallows for the across-enterprise combination of sequential chains thatmay be created by individual enterprises. For example, two differentsequential chains, each used by different organizations that havedisparate database systems (e.g., one organization using Oracle systemsand another using IBM systems), each of which systems keeps track of thetwo separate sequential chains, may be combined via the sequential chainregistry concept provided herein into a single sequential chain, therebyproviding access to information that would otherwise be siloed withineach such proprietary sequential chain. In such manner, therefore, auseful benefit of the SCR systems and methods is the enabling of, whatis commonly referred to as, ‘closed supply chains,’ whereby theconnotation of ‘closed’ (as enabled by SCR) refers to an enclosed datadomain derived from data existing in disparate data domains of differentorganizations and whereby data from such disparate data domainsotherwise may not be conveniently or efficiently cross-relatable as maybe achieved via SCR.

A proprietary sequential chain (or PSC), such as the PSCs 1102, 1134 inFIG. 11, may be comprised of process activities (or PAs) and change ofcontrol actions (or CCAs), as herein earlier described. Also as hereinearlier described, an SCR database architecture may be establishedwhereby PSCs are formed: from (n)-count of SC components, where (n) isan odd whole number; from [(n+1)/2]-count of PAs and [(n−1)/2]-count ofCCAs; and with a PA positioned both at the beginning and at the end of aset of sequential SC components, which together constitute a sequentialchain. Referring to FIG. 11, for instance, sequential chain ‘A’ 1102 maybe comprised of three SC components (such that the (n)-count of three isan odd whole number), including two PAs 1104, 1108 linked by one CCA1106. By way of example but not limitation, the SC component, or PA,1104 may be an oil loading terminal in the Persian Gulf; the SCcomponent, or CCA, 1106 may be an ocean going oil tanker; and the SCcomponent, or PA, 1108 may be an oil unloading terminal in Chennai,India. Thus, sequential chain ‘A’ 1102 is shown, for example, ascomprised of three SC components, including two process activities (PAs)linked by one change of control action (CCA), wherein the (m)-rank forSC component 1108 is three. Similarly, exemplary sequential chain ‘B’1134 is also shown as comprised of an odd whole number of SC componentsof (n)-count 1124, 1128, 1132 and with a CCA positioned between eachsuccessive pair of PAs in that PSC. As will be apparent to an artisan ofordinary skill, alternative system architectures and taxonomies may beemployed. For instance, particular users of the SCR system and methodmay wish to employ a structure whereby SCs may be comprised of an evennumber of SC components; other particular users may wish not to use thedistinction employed in the exemplary taxonomy, as herein described, bynot distinguishing SC components into PAs and CCAs but rather treatingall SCC forms as under one general rubric, e.g., simply as ‘SCC.’

Also as shown in FIG. 11, a mixed sequential chain, or MSC 1112, may beformed by concatenating two uniquely identified PSCs 1102, 1134 with alinking CCA 1110 conjoining these. The resulting MSC 1112, therefore, iscomprised of: (m)-count SC components associated with proprietarysequential chain (PSC) ‘A’ 1102; one SC component, a linking CCA 1110,following the first PSC; and (n)-count SC components associated withproprietary sequential chain (PSC) ‘B’ 1134, which follows the linkingCCA.

Insofar as the schema employed in this example embodiment calls for both(m)-count and (n)-count of SC components in the respective twosequential chains to be odd whole numbers, and since one linking CCA SCcomponent is positioned between the two sequential chains, the resultingcount of (m+1+n) results in an odd number of SC components for the MSC‘C’ 1112. For example, if (m) is 5 and (n) is 9, then an MSC comprisedof two PSCs with (m)- and (n)-count SC components, respectively, plusone linking CCA, would contain 15 SC components. Thus, in this instance,the example MSC 1112 shown in FIG. 11: contains an odd whole number,fifteen, of SC components; begins and ends with an SC component that isa PA; and contains one CCA between each two successive PAs.Structurally, therefore, both PSCs and MSCs are herein shown to beformed so as to contain alternating PAs and CCAs and to begin and endwith a PA. A feature of this structure is that an MSC may readily beformed from two or more PSCs by joining, or plugging together, eachadjoining pair of PSCs together via a linking CCA. Similarly, MSCs mayalso be formed into other MSCs from two or more MSCs or from one or moreMSCs and one or more PSCs by joining, or plugging together, thecomponent segments via linking CCAs. This feature may have utility, forinstance, when one enterprise owns or controls a particular sequentialchain that inter-operates with a different enterprise's particularsequential chain, as is a common practice in global trade, commerce andfinance. Thus, by having a capability for conjoining differententerprises' particular sequential chains into MSCs, the SCR system andmethod enables tracking and tracing of objects (and including aplurality of data attributes and data values pertaining to such objects)through complex sequential chains that may be owned or controlled bymultiple enterprises. Such capability may afford to SCR users and othersparticular benefit in that cross-enterprise data integration becomesachievable, even in circumstances where multiple different enterprisesmay employ multiple different data systems and whereby such dataintegration may not otherwise be possible without SCR.

In other embodiments, other logical schema and arrangements may beemployed for designating the composition of sequential chains fromdiscrete segments (e.g., from SC components) and also for conjoiningsuch sequential chains into larger sequential chains. As will beapparent to an artisan of ordinary skill, mixed sequential chains (orMSCs) may be formed not only from two distinct proprietary sequentialchains (PSCs) plus one linking change of control action (linking CCA),but also from a plurality of other combinations of both PSCs and MSCs.The system and method as described herein enables MSCs to be formed fromany set of conjoined PSCs and MSCs, whereby each pair of adjoiningsequential chains is conjoined by an inter-connecting linking CCA. Forinstance, MSCs may be created by conjoining: two PSCs with one linkingCCA, as described earlier; two other MSCs with one linking CCA; one PSCand one MSC with one linking CCA; or, more generally, any number (k) ofsequential chains with (k minus 1)-count of linking CCAs conjoining eachpair of adjoining sequential chains. Additionally, other schema may alsobe employed.

By employing the schema just described for distinguishing betweenproprietary sequential chains, or PSCs, and mixed sequential chains, orMSCs, an embodiment of SCR may also employ a binary distinction, suchas, for example, as a flag, (that is, a distinction for a particularattribute and attribute value applicable amongst all SC components of aparticular sequential chain) in a plurality of manners. For example butnot by way of limitation, an embodiment of SCR may treat an entire PSCas a sequential chain that possesses a common attribute and commonattribute value amongst all the SC components comprising the sequentialchain. For instance, the ‘1’ condition of such binary distinction for anentire PSC may signify all SC components comprising the particularsequential chain are owned or controlled by a single enterprise. Inturn, the ‘0’ condition of such binary distinction may signify all suchSC components are not owned or controlled by a single enterprise, forinstance, that they are leased by the enterprise establishing theparticular sequential chain. Such binary conditions, as used herein, canbe implemented, in embodiments, as flags set in an SCR database andassociated with such SC components. One utility of such flags may bethat they serve to alert an operator of a plurality of different SCsregarding the degree of control, ownership or inherent risk associatedwith particular SCs.

In embodiments, one such binary distinction may be owned-versusleased-status of SC components within a sequential chain. Another suchtype of binary distinction might be that of enterprise-controlled versusgovernment-controlled status of particular SC components. Alternatively,a plurality of other such distinctions may be employed, depending on thecircumstances and needs in a particular application environment.Further, by enabling such binary distinctions via the construct offorming mixed sequential chains (MSCs) in a plurality of manners, dataanalysis is possible—within an SCR database, within a data analysismodule, or otherwise—such that attributes of entire sequential chains(in addition to attributes of SC components within a sequential chain)may be taken into consideration and analyzed. For instance, anenterprise (or an entire industry or industry sub-sector) implementing aparticular SCR embodiment that distinguishes PSCs as eitherenterprise-owned or enterprise-leased may determine the degree to whichenterprise-produced goods are sold into markets via sequential chainsthat are comprised of entirely- or partly-owned SC components versusthose that are comprised of entirely- or partly-leased SC components.Such data analysis capability may provide utility for assessing anenterprise's degree of sequential chain control, risk and otherattributes.

A plurality of data attributes may be employed to describe a particularsequential chain. In the foregoing, an embodiment of the SCR system andmethod is described whereby: most of a sequential chain's description isderived, or inherited, from data attributes and data values thatdescribe the SC components which comprise a sequential chain; plus oneattribute of an entire sequential chain's characterization—e.g. thebinary discriminant that may be implicit in the distinction between PSCsand MSCs, e.g. enterprise-owned versus leased status of a sequentialchain—plus the unique identifier of the sequential chain. Alternatively,a plurality of attributes may be specified with respect to an entiresequential chain. Embodiments of the SCR system and method may providefor most of the attributes that describe a sequential chain to be thoseassociated with the sequential chain's constituent SC components, ratherthan with an entire sequential chain, such that a sequential chain mayinherit particular attributes from its constituent SC component parts.

A particular benefit of a schema whereby most attributes (and theattributes' corresponding values) of a sequential chain are associatedwith particular SC components, as constituent parts of a sequentialchain, is that the data security protocol and access privilegesstructure of a particular RDBMS (as that system may be employed in anSCR embodiment) may be used to enable user access to data contained inan SCR database on a more granular SC component basis or, alternatively,on a more aggregated sequential chain basis. For instance, animplementation of SCR may be established wherein a plurality of usersmay have access to system-stored data for one or a plurality ofparticular sequential chains or, alternatively, for one or a pluralityof particular SC components, or otherwise. By way of example but notlimitation, a relatively long and complex MSC may be formed such thatparticular users are granted access privileges to data associated onlywith particular sequential chains comprising the MSC or to particular SCcomponents comprising one or more particular sequential chains. In suchmanner, an SCR embodiment may implement and enforce certain look-forwardand look-back data access rules such that particular users may begranted system access only to certain uniquely identified SC components.For instance, in an embodiment for the oil and gas industry, aparticular crude oil trader may be granted system access only to datapertaining to the trader's immediate supplier's sequential chain (e.g.the sequential chain of a crude oil producer selling crude oil to thetrader) and to data pertaining to the trader's customer's sequentialchain (e.g. to the customer's initial SC component, which may be a setof oil storage tanks). A further, general example follows of the benefitderiving from the exemplary structure herein described—e.g., as thisexemplary structure employs discrete, uniquely identified SC componentsto comprise a uniquely identified SC and, further, as thiscomponentization enables particular security protocols and data accesscontrols. By enabling cross-chain association of information existing atall loci and all times within a uniquely identified SC, and withappropriate security protocols and data access controls (as these aretypically available within existing database systems), multipledifferent enterprises co-involved in SCs (e.g., in MSCs) may be morelikely to participate in the sharing of data if they know that they canrely upon specific access controls that will limit particular users, orclasses of users or others, as to the extent of particular data classesthat may be viewed or otherwise accessed from an SCR database.

DocString Identifiers

As herein earlier described, uncovered objects are objects that are notamenable to tracking and tracing by existing systems that employphysical forms of object unique identifiers, e.g. barcodes and RFIDs.For instance, a large lot quantity of crude oil may transit a complex,global sequential chain wherein one particular product (e.g., oneproduct out of many products) created from such raw material input maybe a smaller quantity of refined petroleum product, for example, aparticular lot of diesel fuel contained in a tank truck or a particulardrum of motor oil. In this exemplary instance, a plurality of processesand other steps occurs throughout the sequential chain, whereby a largequantity of raw material (e.g., crude oil) input is converted into manysubsets of product output (e.g. diesel fuel and motor oil) in a mannersuch that the original object (e.g., crude oil) is altered, destroyed orotherwise rendered unusable, changed or ineffective via conversion intosuch derivative products.

In order to provide a form of object unique identifier that continuouslymay be associated with each and all of the original raw material input(e.g. a lot quantity of crude oil), the final product output (e.g. a lotquantity of a particular refined petroleum product, such as petrol) andall object forms that transit a sequential chain in between the firstand final steps of the sequential chain, the document string identifier,or DocString identifier as used herein, is created to provide a form ofobject unique identifier, wherein otherwise an existing form of objectunique identifier (e.g. a barcode or RFID) is not available for purpose.For the example instance just cited, the DocString identifier,therefore, has the effect of a synthetic molecular identifier, wherebythe hydrocarbon molecules contained in the original, source raw material(e.g., crude oil) may be tracked and traced through a sequential chainand, via the SCR system and method, may be linked to the final, outputproducts (e.g., diesel fuel or motor oil in their respective containers)and also to the intermediate products as those intermediate productsexisted prior to the final such product and after the first, source rawmaterial.

FIG. 12 is a block diagram illustrating formation of a DocStringidentifier 1214 and the relation of the DocString identifier to anuncovered object 508, which is given unique identity by such form ofobject identifier. The DocString identifier form of object uniqueidentifier may also be employed to give object unique identification toa covered object in lieu of otherwise, or in addition to, employing aform of existing object unique identifier that may be available to suchcovered object.

A plurality of (n)-count SC components 1202, 1204, 1212 is depicted inFIG. 12 to represent SC components comprising a particular sequentialchain. For instance, by using data entry forms, a system user or anothermay enable an SCR database 220 to receive and store data, via databasesoftware 222 and via a data communications network, whereby such dataestablish the unique identity (and other data attributes) of particularSC components and unique identity of a particular sequential chaincomprised of the particular SC components. Often, in commercialsequential chains, a trade document (or other form of document)accompanies, or is related in some manner to, an object 508 thattransits such sequential chains via a series of SC components. Forinstance, FIG. 12 shows trade documents TD-1 1210, TD-2 1208, and TD-(n)1206 as being associated with the corresponding SC components SCC-11202, SCC-2 1204, and SCC-3 1212. By way of example but not limitation,TD-2 1208 may be a particular bill of lading related to a particular lotquantity of crude oil, as object 508, and to a particular ocean vessel,as SC component-2 1204 (that is, to the ocean vessel as an exemplaryinstance of a change of control action, or CCA, which is a type of SCcomponent herein represented by a triangle such as element 1204).

In embodiments of the SCR system and method, an SCR database 220 mayreceive data via database software and a network from one or a pluralityof systems, users or others, whereby data pertaining to a set of(n)-count of trade documents—for instance, trade documents TD-1 1210through TD-(n) 1206—may be stored in the SCR database 220 as a datastring or otherwise, which, when combined with a data object identifierfor such set of data objects, is referred to herein as a DocStringidentifier. More specifically, in embodiments, a DocString identifier1214 may include: a particular form of data object identifier 1216,which gives unique identity to the entire data object constituting theDocString identifier 1214; and, a particular form of data objectidentifier 1222, 1220 1218, which gives unique identity to each tradedocument 1210, 1208, 1206, wherein each such trade document relates to acorresponding SC component 1202, 1204, 1212 and to the object 508, asthe object exists in a particular form or state in each respective SCcomponent (and wherein an object's particular form or state in one SCcomponent may differ from that in a different SC component, for example,due to successive types of processing of the object within different SCcomponents and/or due to the spatial movement of the object throughdifferent SC components). In embodiments, a trade document (or document)may be any type of information related to the object or to a process ata certain point in the sequential chain. As such, a trade document canbe any type of information regarding the object, sequential chaincomponent, sequential chain component host entity, or sequential chain.In embodiments, such documents may comprise physical documents (e.g.,bills of lading and sales invoices) that are scanned or otherwisedigitized and received into the SCR system. In embodiments, a tradedocument may also be created by entering the information into the SCRsystem, that is, the trade document may not exist prior to entry of thedata into the SCR system. Furthermore, one of skill in the art willappreciate that a trade document may be any item capable of storing suchdata (e.g., electronic data stored in memory, a physical document, orany other data storing mechanism). In embodiments, the data on, orcontained within, the trade document may be converted in order to beentered into the SCR system (e.g., a paper document may be digitized byscanning the document or by inputting the information on it manually).

In embodiments, any suitable form of identifier, such as the GS1'sGlobal Document Type Identifier (or GDTI) or a sequential number, may beemployed for giving unique identity to: the DocString identifier 1214,e.g., as the data object identifier 1216 of the DocString identifier;the trade documents 1222, 1220, 1218; and the SC components 1202, 1204,1212.

In embodiments, the form of object unique identifier employed foridentifying the entire DocString identifier need not, but may, be thesame as the form of object unique identifier employed for identifyingthe trade (or other) documents. Thus, herein has been described, andillustrated with FIG. 12, the manner in which a DocString identifier1214 may be formed within an SCR database 220 and stored (as a datastring or otherwise) by the database for the purpose of giving objectunique identity to an object 508, as the object exists in a particularstate in a particular SC component within a particular sequential chain,whereby otherwise such object (e.g., an uncovered object) may not haveavailable to it an alternative form of existing object uniqueidentifier, such as a barcode or RFID. An SCR database may receive aplurality of data values pertaining to a plurality of data attributesthat relate to an object (and including data constituting a DocStringidentifier 1214), whereby such data is stored as object data 510. Insuch manner, an object data 510 file is stored within an SCR database220, shown in FIG. 12, so that data and information, pertaining to theobject, received by the database may be accessed by users and related toother data with respect to the object's transit through the sequentialchain. Referring further to FIG. 5, an entire set of object data 510 maybe received by an SCR database, whereby, in addition to data being soreceived for the object 508, data is also so received pertaining to eachSC component in which the object exists or has existed and to eachcorresponding SC component host entity 504. Thus, the DocStringidentifier enables an SCR database to receive and associate, or relate,data pertaining to a plurality of data attributes and data values,including data relevant to: the object, as it exists at each SCcomponent; each SC component that hosts the object; and each SCcomponent host entity (and SCC host sub-entity) that hosts each SCcomponent. The capability of a DocString identifier to enable such datarelations for uncovered objects (wherein an alternative form of existingobject unique identifier may not otherwise be available) is one benefitof embodiments of the SCR system and method.

The manner in which a DocString identifier may be stored in an SCRdatabase table is illustrated in FIG. 13. Data table 1300 is anembodiment illustrating how particular object-related data may beassociated, or related, to other such data. Each column in the tableidentifies a particular attribute, e.g. the Name-Item 1302, which givesname to an object as the object exists in a particular SC component.Other attributes may include: name of a particular sequential chain1304, which may host a plurality of SC components, and an ID and name ofa plurality of SC components 1306, which may comprise a sequentialchain. A DocString identifier 1308 may have a particular identifier andmay also have a particular name. The final three columns 1310 in screenshot 1300 illustrate an exemplary identifier for each trade document andgive a name and description of the document. Additionally, other ordifferent data attributes may be employed for describing a DocStringidentifier.

By way of example but not limitation, the set of data 1312, contained inexemplary database table 1300, represents a particular exemplaryinstance of an object's 1302 existence in a particular SC component1306—e.g., a SC component with ID of ‘51’ and name of ‘gatheringlines’—within a particular sequential chain 1304. In this exemplaryinstance, a DocString identifier is given unique identity as ‘7’ andname as ‘Item-15 DocString.’ The last three attributes 1310 in the tableindicate a particular trade document's identifier, the document's name,and a description of such exemplary document, for instance, as ‘metertickets.’ Thus, the element of the DocString identifier used to maintainobject unique identity of object 1302 while that object exists in SCcomponent number ‘51’ is herein illustrated as a particular meterticket, for instance a measurement report indicating the quantity ofobject that flowed through the particular SC component, ‘gatheringlines’ during a particular time interval. In this exemplary instance,the object 1302 is ‘El Morgan crude oil,’ (a type of Egyptian crudeoil). As the object 1302 transits other SC components 1306 within thesequential chain 1304, an SCR database may receive additional datapertaining to the object and its related attributes at each such SCcomponent. The DocString identifier 1308, which gives object uniqueidentification to the object and which is given its own identity as ‘7’in this example, increments in its entire data content as the objecttransits each incremental SC component, for example, from SC componentno. 50 to no. 55, as shown in 1306.

An exemplary instance of application of a DocString identifier is shownin FIG. 14. In embodiments, an SCR system or method may consider amulti-stage sequential chain in a real-world, physical manner orcontext. For instance, FIG. 14 shows such a real-world sequential chain800 comprised of a set of SC components: starting with a producing oilfield and continuing downstream, for instance, to pipelines, storagetanks, oil tankers and to a refinery where crude oil may be refined intopetroleum products. SCR systems and methods then may translate suchreal-world construct into a conceptual form 800 of sequential chain,whereby the particular real-world sequential chain may be conceptualizedto include a set of SC components 802 through 810. That is, as shown inFIG. 14, the sequential chain is comprised of a plurality of SCcomponents, each component related to other components in a definedrelational manner, as recorded in a database, whereby an objecttemporally transits the sequential chain via each such SC component. Inthe exemplary instance illustrated, such object is shown to be aparticular type or grade of crude oil, and the sequential chain is shownto be comprised of an oil field, one or more pipelines and other SCcomponents, culminating at a petroleum refinery.

A particular problem that effectively may be addressed by SCR is nowdescribed, with reference to FIG. 14. In the illustrative real-worldsequential chain 1400 depicted in FIG. 14, an object—in this instance,for example, a lot quantity of El Morgan crude oil produced in Egypt—maybe shown to transit through the conceptually structured sequential chain800 via a set of linked SC components from SC component (1) 802, which,for instance, may be the El Morgan oil field, ultimately to SC component(n) 810, which may be a petroleum refinery at which the exemplary crudeoil may be refined into petroleum products. Such refined petroleumproducts may then transit further downstream, through the samesequential chain 800 as transits the crude oil, that is, throughadditional SC components following SC component (n) 810. Alternatively,such petroleum products may enter into, and transit through, one or aplurality of SC components that comprise a sequential chain differentfrom the one illustrated 800. For illustrative purposes, only the set ofSC components shown for sequential chain 800 are considered, that is,the set of SC components 802 through 810 through which a quantity of ElMorgan crude oil transits to reach a particular refinery, where crudeoil may be refined, or processed, into petroleum products.

A particular problem relative to objects that transit sequential chainsin global trade (and otherwise)—e.g. lot quantities of crude oil,natural gas, mineral ores, agricultural commodities and the like—is theproblem of retaining, relating, and accessing data and informationrelevant to such objects as these transit from one process to another. Arelated problem is that of retaining and accessing data and informationpertaining to the stages or sections of a chain, e.g., to the SCcomponents, through which an object transits and in which objects may beprocessed or otherwise handled. A further, related problem is that ofretaining and accessing data and information pertaining to theattributes and attribute values of: such objects as they exist in eachparticular SC component of a chain and allowing for the fact that suchobjects may or may not be modified within a particular SC component viaphysical, chemical, or other nature of modifications (e.g., viamodification platforms as earlier herein described); such SC componentsthemselves, for instance, data pertaining to ownership, geographic orother attributes of a SC component and including information pertainingto processes that may occur in a SC component whilst an object is in thecomponent; a host entity or host entities (and sub-entities) pertainingto each such SC component; the data describing each such host entity(and sub-entity) that hosts a SC component, for instance, thegeographical information that may describe the host entity of a SCcomponent or measures that may describe the tax status of a particularSC component host entity; and other data and information.

The problem just described may be acute for objects that otherwise maynot be amenable to track and trace operations via existing methods suchas by use of RFIDs or barcodes placed on the object. That is, theproblem described may be acute for uncovered objects, as such objectsare herein earlier described. Application of the DocString identifierform of object unique identifier, via the SCR system and method, solvesthis data retention and access problem for uncovered (and covered)objects. The DocString identifier enables continuous tracking andtracing of uncovered objects by: associating a uniquely identified trade(or other) document pertaining to the object as it exists at or in aparticular SC component with all other such documents pertaining to theobject (including such object in a modified form) as the object existsat or in all other SC components within a particular sequential chain;employing a form of unique identifier for each such unique document;linking together all such uniquely identified documents, each onerelating to the object as it exists (or existed) in an SC componentincluded within the sequential chain; giving a form of uniqueidentifier—e.g., the DocString identifier—to the entire data set ofunique identifiers for the corresponding such documents; and employingthat form of unique identifier (the DocString identifier) as a means forgiving continuous object unique identity to, what are herein referred toas, uncovered objects.

For instance, as shown in FIG. 14, a lot quantity of crude oil, as anobject 1302 in database table 1300, may have commenced transit of asequential chain 800 at the El Morgan oil field, e.g., as SC component 1802, and been identified at that SC component via a particular tradedocument, shown in the figure as TD-500/50, field production record. Theobject 1302 may continue transit through a sequence of SC components,finally reaching and transiting SC component (n) 810, which, forinstance, may be a petroleum refinery. For each SC component in thisexemplary instance, an SCR database may be informed of a particulardocument associated with the object for each particular SC component,culminating in the illustrative refinery-related trade document, shownin the figure as TD-500/55, distillation unit meter record.

The entire set of trade documents 1310 may then be related and stored inan SCR database, with such set given its own unique identifier. For theillustrative instance shown in FIG. 14, each particular trade (or other)document may be given (by a system user or another) a unique identity,such as via a GDTI (e.g., GS1's global document type identifier), andthen the grouping, or set, of such uniquely identified documents alsomay be given (by a user or another) a single unique identity 1308. Forinstance, in FIG. 14, a single DocString identifier 1308 may be assigneda unique sequential, numerical identity of ‘7’ and/or a unique name of‘Item-15 DocString.’ Such DocString identifier, as a data objectcontained in an SCR database, enables an uncovered object to becontinuously identified as such object transits a sequential chain thatis maintained within an embodiment, including an uncovered object thatmay undergo physical, chemical, or other nature of changes within SCcomponents of such sequential chain. Such continuous identification ofan uncovered object like crude oil and derivative products of crude oilmay not otherwise be possible through use of existing object uniqueidentifier forms such as barcodes and RFIDs even though such other formsof object unique identifiers may be viable for particular (typically,downstream) segments or components of a sequential chain such as asupply chain.

With such unique object identifier, that is, with a DocString identifierformed as described, the exemplary object—e.g., a lot quantity of liquidcrude oil, as such object may initially exist in form—may have itsunique identity preserved throughout the entire sequential chain 800,which may be comprised of a plurality of SC components. With this mannerof continuous identification of an object (which object may nototherwise be amenable, continuously through a sequential chain, toholding an existing form of identifier, such as an RFID or barcode), thecontinuous, uninterrupted identification of objects may be maintained asobjects transit through (and may be modified within) sequential chains.Thus, the DocString identifier form of object unique identifier cansolve the problem of how to track and trace uncovered objects throughsequential chains, wherein, otherwise, such ability to track and tracemay not be available. Further, via the construct of mixed sequentialchains, or MSCs, the DocString identifier can also solve this problem inenvironments where uncovered objects transit complex sequential chains,or SCs, that are comprised of chains operated by more than oneenterprise and also wherein multiple enterprises may employ differentforms of sequential chain management systems (e.g., different forms ofsupply chain management systems, or SCM systems). Within the SCR systemand method, therefore, the combination of the DocString identifier withother SCR system capabilities, as herein described, enables anembodiment to provide a plurality of functions including but not limitedto: receiving otherwise inaccessible data relating to uncovered objects;storing such data in a relational (or other form of) database; relatingsuch data to other data stored in the relational (or other form of)database; relating such data to other data stored in other data systems,to data stored in enterprise data systems and to data stored in globaldata synchronization networks; manipulating such data in a data analysismodule; and responding to users' search queries for such relational,manipulated, and other data. As will be apparent to an artisan ofordinary skill, such capabilities of the SCR system and method arelogically available to system users and others with respect to objectsthat are not uncovered objects, e.g., with respect to covered objects.For example, the DocString identifiers for objects transiting throughtheir own respective SC may be combined into a new DocString identifierthat uniquely identifies the combined object created when two or moreobjects come together (e.g., a blended object), and then may be brokeninto two separate DocString identifiers to capture the fact that theblended object may be split at a later time. As such, DocStringidentifiers may be combined and split any number of times as an objecttraverses a sequential chain. In other embodiments, separate DocStringidentifiers may be maintained through blends and splits by addinginformation from other DocString identifiers as necessary to identifyother sequential chains that are introduced and split away at differentpoints.

An example of the benefit of such capabilities, as herein described, isgiven with respect to large lot quantities of crude oil that may betransported to and processed in a petroleum refinery, from which refinedpetroleum products may be further transported to customers, including,for instance, such products as refined aviation fuels, gasoline, anddiesel fuels. For a plurality of reasons—for instance, for reasons ofcompliance with local, regional, national, or international regulations(whether of a mandatory nature of regulation such as by law [e.g., bythe U.S. Dodd-Frank Act] or via a form of voluntary regulation such asmay be promulgated by an international organization [e.g., by theEITI])—a purchaser of petroleum products, e.g. of diesel fuel, may wish,or be required, to be aware of particular attributes pertaining toorigins or other characteristics that describe the crude oil processedin a petroleum refinery and from which crude oil such petroleum productsmay be derived. As an example of uncovered objects, a lot quantity of,say, diesel fuel may not be amenable (e.g., via existing systems such asthose using RFIDs or barcodes) to being accurately described, orcharacterized or classified, in terms of the crude oil source(s) used toproduce such diesel fuel or to facts and circumstances pertaining to thesequential chains and SC components through which crude oil transitsfrom source to refinery or through which diesel fuel transits fromrefinery to customer. Another example of an uncovered object type, whichis amenable to the SCR systems and methods, is water, for instance wateras an input resource to the production of soft drinks and otherbeverages. The Aqueduct Alliance (a multi-stakeholder initiative backedby seven large U.S. corporations and by the World Resources Institute,an environmental campaign group) is launching in 2011 a new databaseshowing water availability at a local level. Enterprises, such asCoca-Cola, producing and marketing soft drinks, may wish to enhancetheir product's brand image (and/or the image of the enterprise itself)or otherwise differentiate their product by providing customers (viasuitable user interfaces, such as via a smartphone app) information thatallows the prospective buyer of a soft drink product to be informedregarding the source/origin of water used in producing suchproduct—e.g., showing the statistical likelihood that ‘sustainablesources of water’ are employed in the production of the product asoffered for sale at a particular store. In this example, insofar as such‘sustainably-sourced water’ may be an attribute measured or otherwisedetermined by a third-party entity, such as the Aqueduct Alliance, datasupporting such attribute is an example of data that may be stored, andaccessed from, outside an SCR database, for instance as shown in FIG.19, from an enterprise data system 1902 or a global data synchronizationnetwork 1904.

The problem of acquiring, relating and providing (e.g., to customersand/or regulators) such information for uncovered objects—that is,information encompassing an uncovered object's existence from originalsupplier to final customer (or a subset of such information)—may besolved via embodiments of SCR by enabling continuous identification ofsuch objects with a DocString identifier in conjunction with othercapabilities of an embodiment, as herein described. As a furtherexample, for instance, a diesel fuel customer in a particular countrymay be required by regulation (or otherwise) to ensure that itsparticular diesel fuel purchases meet a test that proscribes purchase ofsuch fuel in circumstances where the fuel has been derived from crudeoil sources originating in any country that is included in a list ofsanctioned countries, as such list may be maintained by, say, the UnitedNations or another body. Given the complexity of supply chains (whereinsuch chains are an example of sequential chains) through which crudeoil—as an instance of an uncovered object type, as herein used—oftenmoves and is transformed into marketable petroleum products, existingsystems may not be able to ensure continuous identification of suchobject and of the products derived from such object, particularly whensuch object undergoes changes of form such as via physical or chemicalprocesses that may occur in a petroleum refinery. Thus, in the exemplaryinstance of a purchaser of diesel fuel, such purchaser can be enabled tocomply with the exemplary instance of regulation (e.g., concerningdiesel fuel being sourced from non-sanctioned crude oil producingcountries) by use of an embodiment of SCR, whereas such compliance maynot otherwise be achievable by other systems. Many other real-worldexamples exist, whereby mandatory and/or voluntary regulation proscribeparticular uses of particular object types with particular attributes,for instance: the U.S. Defense Authorization Act 2007, which treats withrare earth minerals used in United States defense procurementoperations; the U.S. Dodd-Frank Act 2010, which treats with particularresources sourced from the Democratic Republic of Congo; the Roundtableon Sustainable Palm Oil, or RSPO, which deals with sustainably-sourcedpalm oil; the Kimberly Process, dealing with ‘transparent’ (non-‘blood’)diamonds; and the Extractive Industries Transparency Initiative, orEITI, which seeks to disclose measures of fiscal transparency concerningfinancial payments by companies, and receipts by government bodies,relating to oil, gas and non-hydrocarbon minerals. In all these notedexemplary instances and in others, the available information required(via mandatory regulation, such as Dodd-Frank) or suggested (viavoluntary regulation, such as via RSPO and EITI) may either be providedin the first instance (or significantly enhanced) through use ofembodiments of SCR systems and methods.

A plurality of other exemplary instances may be described, whereby aconsumer of uncovered objects—at any point in a sequential chain—maywish, need, or be required, to know particular information pertaining toobjects either being purchased by, or sold to, that consumer. Forinstance, a buyer of crude oil may be required to verify all channels(e.g., SC components) through which the crude oil has been handled,including, for instance, verification of: the nationality of any or allof the SCC host entities that host each SC component through which thecrude oil has transited; the identities of parties handling the crudeoil throughout the sequential chain; whether or not the crude oil wasproduced in a country that is a member of a particular transparencyorganization; and other facts and circumstances. In such respect, forinstance, embodiments of the SCR system and method may facilitate forenterprises and others their compliance with international (or other)sanctions regimes that may be promulgated to control the global flows ofparticular forms of sanctioned natural resources, such as crude oiloriginating from a sanctioned country or refined products formed fromsuch sanctioned natural resources. By way of further example but notlimitation, the SCR system and method may be used to assist U.S.SEC-listed enterprises in complying with particular provisions of theDodd-Frank Act with respect to not dealing with, or acting as, suppliersof natural resources originating in a particular country. The SCR systemand method, further, can assist such enterprises in such form ofcompliance in the event that compliance is extended to include not onlyproscribed natural resources from proscribed countries (e.g., proscribedvia the U.S. Defense Authorization Act 2007) but also intermediate andfinal products created from such proscribed natural resources, whereinsuch resources may be in the form of uncovered objects as hereindescribed. As one skilled in the art may appreciate, many other examplesexist, for instance, with respect to mandatory regulations pertaining tomoney laundering.

Insofar as crude oil may be considered an example of uncovered objects,as herein described, an embodiment's use of the DocString identifierenables the continuous identification of an object such as a large lotquantity of crude oil, thereby, further enabling a diesel fuel purchaserin this exemplary instance to obtain particular information such as maybe required pursuant to regulation (or otherwise). A benefit of the SCRsystem and method, therefore, is the enabling of acquisition, relation,manipulation, storage, and dissemination of such information pertainingto uncovered objects, where otherwise, such uncovered objects may not beamenable to tracking and tracing via other systems, thereby preventingthe capacity to capture and retain particular classes or types ofdesired information in the first place

Example User Interface

For purposes of convenience, data accuracy, and other reasons, anembodiment of the SCR system and method may employ one or a plurality ofdata entry forms, whereby users may enter data into such forms andthereby enable an SCR database to receive particular data. Inembodiments, it is also noted that forms, tables, queries and reportsmay be received into the SCR database first as templates, that is, asblank formats created by a system designer or another for later use bySCR system users. Such templates for forms, tables, queries and reportsmay be received by the SCR database and stored therein as data objectsand may be modified from time to time.

FIG. 15 is an embodiment of a data entry form 1500 that can be suitablefor the enabling of an SCR database to receive data, which may beentered into such exemplary form and, thereby, declared by an SCR systemuser and, thus, received by a database. In this exemplary instance, dataform 1500 pertains to a database entity class for the entity named ‘SCcomponent,’ that is, for a building block of a sequential chain (in theinstance portrayed in FIG. 15, a particular form of SC component, viz.,a SCC comprising a segment of a ‘PSC’ or proprietary sequential chain).For clarity, it is noted that such entity (that is, the entity SCcomponent) previously will have been established as a data object in theSCR database, pursuant to the procedure described earlier. As will beapparent to an artisan of ordinary skill, other data entry forms maysimilarly be created and stored as data objects in an SCR database for aplurality of other database entities that similarly have been previouslyestablished. For example but not limitation, such entities and theircorresponding data entry forms may be created and stored in an SCRdatabase for the entity classes of: objects that exist and move insequential chains; sequential chains; SC components, which comprisesequential chains; SC component host entities that host SC components;and other database entities.

A data form, such as example form 1500 shown in FIG. 15, enables an SCRdatabase to receive particular data pertaining to a particularsequential chain and to particular SC components. For instance, a usermay wish to cause an SCR database to receive and store data pertainingto a uniquely identified sequential chain, such as the one described inFIG. 14, comprised of (n)-count of uniquely identified SC components.Exemplary data entry form 1500, as it may be received by and stored inan SCR database, may be used to enable the digital formation and storage(also in an SCR database) of data pertaining to such a sequential chain,comprised of a plurality of SC components, whereby each such SCcomponent may have a plurality of data attributes and corresponding datavalues that describe it. For instance, exemplary data entry form 1500includes a plurality of data attributes and corresponding data values toidentify and describe a particular SC component, such as the SCcomponent of FIG. 14, which is one SC component comprising the exemplarysequential chain. Similarly, data form 1500 may be employed to enable anSCR database to receive data pertaining to a plurality of or all the SCcomponents that comprise a particular sequential chain, thereby enablingrelation, or association, amongst the SC components comprising aparticular sequential chain.

An SCR database may receive data via data entry forms, such as exemplaryform 1500 depicted in FIG. 15, for forming and describing a particularsequential chain and the SC components comprising the particularsequential chain by one of a plurality of methods, depending on theneeds and requirements of a particular application environment. Forinstance, in one method of operation, an SCR database may receive datavia data forms, such as form 1500, over a time period corresponding tothe movement of an object through a sequential chain. As used herein,such method of operation is referred to as a continuous-formation methodor mode.

In embodiments, whereby an SCR system and method is operated incontinuous-formation method, an SCR database may receive data describinga sequential chain 800 and a plurality of SC components 802, 804, 806,808, 810 (FIG. 14) from one or a plurality of system users over a periodof time rather than at a single time. For example but not limitation, aparticular sequential chain's set of all SC components may not be fullyknown in advance at the time an object enters the first SC componentcomprising the sequential chain. In such instance, an SCR database mayreceive data via data entry forms, such as form 1500, at a plurality ofdiscrete times, for example, at the times at which an object enters orexits each discrete SC component. For example, at the time when a lotquantity of crude oil exists in an SC component named ‘field storagetanks,’ subsequent (or downstream) SC components, such as a particularoil tanker or a particular refinery that may later host the same object(or the same object as it may be subsequently modified), may not yet beknown. Data for such downstream SC components may be received by an SCRdatabase via suitable data entry forms at later times than when thefirst SC component data is received by the SCR database. Such is anexample of a continuous-formation method of SCR.

In other embodiments, another method of operation is referred to hereinas front-end-formation mode. An SCR system functioning in thefront-end-formation mode is one whereby an SCR database may receive datapertaining to sequential chains and their constituent SC components allat one time or, alternatively, at only a few particular times, ascontrasted with the continuous formation-method of operation describedabove. The front-end-formation method of operation may be moreconvenient for application by system users in instances where aparticular, complete sequential chain may be known in advance of objectsentering into such chain and also wherein such chain may be expected toremain invariant over a longer time period, as to its constituent SCcomponents comprising the sequential chain. In such instances, users mayfind it convenient to enable an SCR database to receive data pertainingto a sequential chain and its constituent SC components, via data entryforms or otherwise, in advance of a period of time during which suchsequential chain is expected to remain invariant for a particular timeperiod.

By way of example, but not limitation, of the front-end-formation methodof operation, data for a particular sequential chain may be received by,and stored in, an SCR database for SC components including, forinstance, a particular producing oil field comprised of a plurality ofoil wells, particular oil gathering lines, a particular field transitpipeline, and particular oil storage tanks at a particular harbor. Insuch circumstances, an SCR system user may observe that all such SCcomponents are fixed assets and are unexpected to change for, say,several years or to be substituted by other such SC components(although, ex post facto, they may be so substituted in which event theSCR system and method, nonetheless, accommodates such initiallyunplanned change). In such example, the front-end-formation method ofSCR system operation may be more suitable than the continuous formationmethod of operation. For clarity, however, it is also noted that thefront-end-formation method of operation still allows for the SCRdatabase to receive new or updated data pertaining to particular dataattributes and data values relating to a plurality of SC components forwhich data attributes and data values earlier may have been received bythe SCR database. For example, the SCR database may receive a new datavalue corresponding to a particular data attribute for a previouslydeclared SC component, whilst that SC component itself is notsubstituted with a different SC component.

As will be apparent to an artisan of ordinary skill, other methods ofoperation, in addition to the two just described, may also be employed.For instance, an SCR database might receive data pertaining tosequential chains and SC components in a multiple-batch mode, wherebysuch data may be received via data entry forms, such as form 1500 inFIG. 15 or otherwise, in more than a single batch as for thefront-end-method but in fewer batches than in the continuous-formationmethod.

Regardless of the method of operation by which an SCR database mayreceive data pertaining to sequential chains and SC components, datapertaining to objects hosted by sequential chains and by sequentialchains' SC components, as well as data pertaining to SC component hostentity attributes, may be received by the SCR database as frequently ascircumstances warrant. For instance, when a particular lot quantity ofliquefied natural gas, or LNG, is re-gasified at a re-gasificationfacility after being discharged in liquid form from a cryogenic LNGtanker, an SCR database may receive new data attributes and data valuespertaining to the object because the object will have been modified inform from liquid to gas state. In a similar manner, data attributes anddata values may change for a SC component host entity even though the SCcomponent itself may remain invariant over time. For example, an SCRdatabase may contain data describing a particular SC component as‘company owned,’ and may later receive data updating such ownershipattribute to indicate that the same SC component has changed to a‘leased’ status of ownership—even though the SC component itselfphysically has not changed in this example.

Exemplary data attributes and some of their corresponding exemplary datavalues are shown in FIG. 15 for the exemplary data entry form 1500,including, for instance, attributes and values for: the unique identitynumber 1502 that identifies an exemplary sequential chain (such assequential chain 800 shown in FIG. 14), shown as ID number ‘1’ in FIG.15, whereby the particular, identified sequential chain hosts aplurality of SC components; the name of the exemplary sequential chain1504, shown as ‘Name-PSC-100;’ the unique identity number for theenterprise 1506 that owns or controls the sequential chain; the uniqueidentity number for the particular SC component 1508 contained in theidentified sequential chain 1502; the SC component type 1510, by whichis meant either a process activity (PA), as shown in the exemplary dataform, or a change of control action (CCA), as these two terms are hereinearlier described; a component rank 1512, by which in this example ismeant the serial rank order in which a SC component exists in asequential chain, starting with rank order 1 and ending in rank order(n), as depicted in the model shown for a sequential chain 800 in FIG.14; the name of the SC component 1514, for instance ‘oil field;’ adescription of the SC component 1516, for instance, ‘producing wells X,Y, Z’; the name of the mixed sequential chain (MSC) 1518, if any (whichterm, MSC, is defined and described later below), which MSC contains theparticular sequential chain 1502, 1504 in which the SC component 1508 isfurther contained; the type of SC component host entity 1520 that hoststhe SC component, for instance, the type ‘country;’ the name of the SCcomponent host entity 1522, for instance, ‘U. K.’ as the particularinstance of the host type 1520, ‘country;’ and an MSC segment flag 1524,which is also herein below further described and illustrated with FIG.16. An artisan of ordinary skill will observe that the exemplary dataentry form 1500, absent data values, represents a construct for listingone or more data attributes (for instance, ‘Type of Host’ 1520)pertaining to a database entity (for instance, to ‘PSC’ representing theconstruct of a proprietary sequential chain) and that such data entryform also contains blank data entry fields whereby a database mayreceive particular data values related to particular data attributes(for instance, ‘Country’ 1520 as the particular exemplary data value forthe particular data attribute ‘Type of Host’). Thus, in this example,‘Type of Host’ may be a data attribute, and ‘Country’ may be a datavalue for such data attribute. The capability, within an embodiment ofan SCR system and method, to allow for hierarchical data is shown indata form 1500, for instance, in the hierarchical data arrangementwhereby ‘U.K’ is shown as a data value for the data attribute, ‘Name ofHost’ 1522 and, in turn, whereby ‘U.K.’ is an instance of ‘Country’where ‘Country’ is a data value for ‘Type of Host’ 1520 as one type ofdata attribute ‘Type of Host.’ Such capacity for handling tiered orhierarchical data is typical in extant relational database systems.

A particular data entry form—such as the exemplary form 1500 shown inFIG. 15 for use in enabling an SCR database to receive data pertainingto a SC component 802 comprising a segment of a sequential chain 800, asthese are shown in FIG. 14—may be created by a system designer oranother for use by system users for all instances of all database entityclasses. Thus, for instance, data entry forms also may be created by asystem designer or another and received by and stored in an SCR databasefor a plurality of other database entities, including for the entitiesof: objects, which exist and move within sequential chains, and for thehost entities that host SC components.

Referenced in FIG. 15 are several exemplary data attributes pertainingto declaration of data by user input, and receipt of data by an SCRdatabase, relating to formation of uniquely identified sequentialchains. An identifier 1502 is specified to give unique identity to aparticular sequential chain, in this example to a proprietary sequentialchain, or PSC. A name of the PSC 1504 may also be specified, as may theunique identifier of the enterprise 1506 having a particularjurisdiction for, or interest in, the sequential chain. Among theplurality of data attributes shown in form 1500 is a field 1524 fordesignating whether a particular sequential chain—in this exemplaryinstance, the PSC with ID of ‘1’—is associated with, and a part of, amixed sequential chain and, if so, the name of the MSC 1518 in which thePSC is a constituent part. Further descriptions of the manner in whichdata is received by an SCR database are provided elsewhere herein.

The form of identifier employed in a particular embodiment of the SCRsystem and method to assign a particular, unique identity to aparticular data object in an SCR database may be one of a plurality ofobject unique identifier systems. For instance, the GS1 organization'sform of object unique identifier known as the Global Individual AssetIdentifier, or GIAI, may be used in a particular SCR embodiment to giveunique identity to particular sequential chains, corresponding to dataentry field 1502 in FIG. 15. Alternatively, other such forms of objectunique identifier may be used, for instance, a sequential numberingsystem. A particular form of object unique identifier, as describednext, may be created within an SCR database for use with uncoveredobjects, as this object type is herein earlier defined.

Although example user interface and data entry forms are provided, oneof skill in the art will appreciate that the user interface and dataentry forms are provided for illustrative purposes. Other types of dataforms and user interfaces may be employed with the embodiments disclosedherein.

Creating a Unique Identifier

FIG. 16 is a flow chart illustrating an example embodiment of a method1600 to create a DocString identifier. The method 1600 may be employedto create a DocString identifier, as previously described with respectto FIGS. 12-15. In embodiments, the method 1600 may be performed by adatabase or a general computing device. Flow begins with operation 1602where a sequential chain is registered. Registering a sequential chainassociates the sequential chain with a unique identifier that may beused to relate an object with data as it traverses a sequential chain.In embodiments, the DocString identifier is created upon registering thesequential chain. In such embodiments, the DocString identifier is theunique identifier created upon registering the sequential chain. Inother embodiments, the DocString identifier may be a modification of aunique identifier created upon registration. For example, the DocStringidentifier may be created by modifying the unique identifier using anoperation such as a hash and/or by combining the unique identifier withother data. One of skill in the art will appreciate that any manner ofcreating a unique identifier may be employed at operation 1602.

Flow proceeds to operation 1604, by which the database receives a firstdata item. For example, the database may receive the initial objectdefinition from a user of the database, a user using a differentcomputer device connected to the database over a network, or by anothersystem, application, or process in communication with the database. Inembodiments, the first data item may be received from a first user at afirst location. In one embodiment, a user interface such as the exampleuser interface provide in FIG. 15 may be used to gather and then senddata defining the first data item that the database receives atoperation 1604. In embodiments, the first data item may be a data objectcontaining information about an object, such as, an object passingthrough a sequential chain, such as, for example, oil passing through anoil supply chain. In embodiments, the first data item may contain anytype of data related to the data object.

In embodiments, the first data item may be associated with a unique ID.In one embodiment, the unique ID may be received at operation 1604 alongwith the data item. In another embodiment, the database or generalcomputing device performing the method 1600 may create a unique ID forthe first data item upon receiving it. For instance and referring toFIG. 12, such first data item may pertain to a trade document, TD-11210, as such document pertains to an object 508, such as a lot quantityof crude oil as the object exists in SC component 1202. Such data item,as it pertains to a particular trade document, may, for instance,pertain to a document such as a trade invoice, a customs document, anassay document or other form of business or other document that,regardless of its particular documentary purpose, has the capability toeffect specific linkage of the object of interest to the SC component inwhich the object may exist at a time or in a time interval and, further,to effect similar linkage of the object of interest to other SCcomponents that are included with the first SC component 1202 in acommon sequential chain. In other embodiments, the data may be createdat operation 1604.

Flow continues to operation 1606, where an additional data item isreceived. In embodiments, the additional data item may be a sequentialchain component, a sequential chain component host, an object, or anyother type of data related to a sequential chain. In embodiments, theadditional data item may be received by a second user that is differentfrom the first. Furthermore, because the method disclosed herein iscapable of tracking object information as an object traverses asequential chain, such as, for example a supply chain, the additionaldata item may be received from a different location than the first dataitem. In embodiments, the additional data item may include its ownunique ID. In another embodiment, the method 1600 may create a unique IDfor the additional data item upon receiving it.

Flow continues to operation 1608, where the DocString identifier ismodified using the unique ID of the additional data item. Inembodiments, the DocString identifier may be modified by concatenatingit with the unique ID of the additional data item. In other embodiments,the DocString identifier may be modified in another manner, such asperforming a hash on the DocString identifier using the unique ID of theadditional data item. In other embodiments, the data item may be storedwith the DocString identifier, thereby allowing all the relateddocuments to be pulled and analyzed when accessing the data item. One ofskill in the art will appreciate that any manner of modifying theDocString identifier may be employed with the embodiments disclosedherein.

Flow then proceeds to operation 1610, where a relationship is createdbetween the first data item and the additional data item or items. Inone embodiment, the relationship is created using the DocStringidentifier. For example, the first data item and the additional dataitem may each be stored in a relational database along with theDocString identifier. The DocString identifier is used to relate thedata items, for example, by acting as a primary or secondary key foreach database entry corresponding to the first data item and theadditional data item. In embodiments, the relation of the first dataitem and the additional data item or items creates a sequential chain.The relation of the first data item and the one or more additional dataitems allows for the tracking of an object (e.g., the first data item oran object) to be tracked as it travels a sequential chain, representedby the additional data items (e.g., sequential chain components,sequential chain component hosts, etc.)

Flow continues to decision operation 1612. At operation 1612 adetermination is made as to whether the sequence has completed. Forexample, the method 1600 may receive an indication that the sequence iscomplete. One of skill in the art will appreciate that any matter ofdetermining that a sequence has completed may be employed with theembodiments disclosed herein. If the sequence is complete, flow branchesYES and terminates, resulting in a completed sequential chain for theobject. If the sequence is not complete, flow branches NO and returns tooperation 1606 where additional data items are received and theDocString identifier is again modified, thereby continuing constructionof the sequential chain.

In embodiments, the method 1600 may be employed using afront-end-formation mode of data entry, a continuous-formation mode ofdata entry, a combination of both or another mode of data entry. One ofskill in the art will appreciate that the first data item and the one ormore additional data items may be received at the same time or at latertimes.

Referring now to FIG. 17, flow chart illustrating an embodiment of amethod 1700 for adding data to a sequential chain. The method 1700 maybe employed to form data entities and data relationships. Inembodiments, the method 1700 may be performed using a database, such asSCR database 220 or a general computing device. Flow begins withoperation 1702 where object data is received. In embodiments, objectdata may be data regarding a covered object, an uncovered object, or anyother data related to any type of object, including tangible andintangible objects, capable of traversing a sequential chain. Flowcontinues to operation 1704, where the object data is stored. Inembodiments, the object data may be stored as an object. In otherembodiments, the object data may be stored in a relational database as atable entry. One of skill in the art will appreciate that any manner ofstoring the object data may be employed with embodiments disclosedherein.

Flow continues to operation 1706, where the method 1700 creates aDocString identifier. The DocString identifier may be created andmodified as described with respect to FIG. 16. In embodiments, theDocString identifier is used to identify and relate data received whileperforming method 1700. Flow continues to operation 1708, where movementdata is received. In embodiments, movement data may relate to the objectas it moves through time in a sequential chain. In other embodiments,movement data may correspond to actual movement of the object, a changein the object, or any other type of data indicating that the object hasprogressed through a sequential chain. Flow continues to operation 1710,where the movement data is stored. In one embodiment, the movement datamay be stored as a sequential chain component. In other embodiments, themovement data may be stored in a relational database as a table entry.One of skill in the art will appreciate that any manner of storing theobject data may be employed with embodiments disclosed herein.

Flow continues to operation 1712, where entity data is received. Inembodiments, entity data corresponds to an entity at a particular pointin time or a particular time interval. For example, the entity mayrelate to the location of the object at the particular point of time.Non-limiting examples of entities include countries, companies,pipelines, vessels, containers, or even non-tangible processes. Inembodiments, although not shown, the entity data may be related to themovement data upon its receipt. Flow proceeds to operation 1714, wherethe entity data is stored. In one embodiment, the entity data may bestored as a sequential chain component host. In other embodiments, theentity data may be stored in a relational database as a table entry. Oneof skill in the art will appreciate that any manner of storing theobject data may be employed with embodiments disclosed herein.

Flow continues to operation 1716, where a sequential chain is created.In embodiments, the sequential chain is the relation between the objectdata, movement data, and entity data. In such embodiments, the creationof the sequential chain includes creating a unique identifier for thesequential chain that is used to relate all information that is a partof the sequential chain. Although the sequential chain is described asbeing created in operation 1716, this step may be performed at thebeginning of method 1700 or at any other point. In embodiments, theobject data, movement data, and entity data may be related using theDocString identifier. In embodiments, the sequential chain may be storedas a sequential chain object previously discussed. Although constructionof the sequential chain object is showed at operation 1716, one of skillin the art will appreciate that the sequential chain may be constructedat any time during method 1700. For example, the sequential chain may beconstructed upon first receiving the object data. In such embodiments,the sequential chain will be continuously modified as other data (e.g.,movement data, entity data, etc.) is received.

Flow proceeds to operation 1718, where operation data is received. Inembodiments, operation data is additional data, beyond that which isreceived during the phase in which a sequential chain is constructed. Byway of example but not limitation, operating data may include: instanceclass data, e.g. data that describe a plurality of particular oil wells(as entity instances) for the entity class ‘oil well;’ new entity classdata, e.g. data that describes additional database entity classes thatare not earlier received by the database, such as ‘Ocean Vessels’ as anentity class; search queries, which are data objects that enable thedatabase to receive a user's specification of particular data that is tobe searched within, formatted by, and returned from the database to theuser; results tables, which may be created within the database from aplurality of database tables and which compile and convey desiredinformation to a user in response to the user or another firstspecifying the content and format of such tables; results reports, whichalso may be created within the database from a plurality of databasetables and which compile and convey desired information to a user inresponse to the user or another first specifying the content and formatof such reports; and other forms of data objects.

Operating data, such as that just described, are formed into appropriatedata objects in the same manner as also earlier described for formingdata entities and entity relationships. That is, appropriate data entryforms may be employed to enable an SCR database to receive data from asystem user or another. By use of such data entry forms, which formsthemselves are stored as data objects in the SCR database, desiredsource data may be received by and returned from the database.

In addition to the particular operations for enabling an SCR database toreceive operating data, there may be other nature of database operationsthat relate to data protection, data verification, computer systemmaintenance, software updates and upgrades, system security, and aplurality of other conventional or other operations relevant toeffective, efficient, safe operation of the platforms on which an SCRsystem and method operates. Further, there is a plurality of methods andmeans by which the method 1700 may inter-operate with existingenterprise data systems and existing global data synchronizationnetworks. The maintenance and general operation of such existing,external systems is not herein described.

Flow continues to operation 1720, where the operation indicated by theoperation data is performed. Although the method 1700 has been describedas discreet steps performed in a particular order, one of skill in theart will appreciate that the order of the steps may be changed.Furthermore, while the method 1700 described receiving one instance ofobject data, movement data, and entity data, one of skill in the artwill appreciate that any number of instances of such data may bereceived. For example, in a blend or split platform object data maychange (e.g., new objects may be created). In other embodiments,multiple instances of movement data and entity data may be received bythe method 1700. One of skill in the art will appreciate that the method1700 may be employed to create the entities and relationships describedherein such as, but not limited to, the entities and relationshipsdescribed with respect to FIGS. 2-11. Accordingly, the method 1700 mayoperate upon any of the data, entities, and relationships describedherein. Furthermore, one of skill in the art will appreciate that themethod 1700 is extendable such that it may operate upon different setsof data not described in the present disclosure.

Example SCR Systems

FIG. 18 is a block diagram illustrating components of an exampleembodiment of an SCR system 1800, including illustration of the mannerin which data is received by an SCR database 220 and may be returned tousers 102, 104 following manipulation of data so received. An embodimentof SCR system and method 1800 may include, inter alia: i) a networkcommunications system that facilitates data and other communicationbetween a system facilitator 102 and a plurality of other users 104 withan SCR database 220 via exemplary database software 222; and ii) a dataanalysis module 1810. System users 102, 104 and including a systemdesigner (collectively referred to herein, as users) may use anappropriate remote device 1802, such as a desktop or laptop computer, atelephone or smartphone, PDA or other suitable electronic device, toaccess the exemplary database software 222 and SCR database 220 througha network 1806, such as the world wide web or an intranet, via acommunications link 1804. In embodiments of SCR 1800, the exemplarydatabase software 222 and SCR database 220 may be accessed by users viaa suitable user interface 224, which may also enable access to a dataanalysis module 1810.

SCR system 1800 includes a software platform 222, executing on one ormore computers, for example web or application servers, that are incommunication with SCR database 220, which database also executes on oneor more computers. Software platform 222 may include a form of databaselanguage 226. Database language 226 may include: a data definitionlanguage 228, or DDL; a data manipulation language 230, or DML; and adata control language 232, or DCL.

DDL 228 is a part of a database language 226 used by a system designeror another to: create a particular database and structural components ofthe database; modify the structure of an existing database; and destroya database after it is no longer needed. DDL 228 is employed to createstructural elements, including, for instance, data schemas, data tables,and data views. DML 230 is a part of a database language 226 used by asystem designer or another to operate on data that inhabits a datastructure created via the DDL 228, including operations to: store datain a structured way that makes data easily retrievable; change storeddata; selectively retrieve information that responds to a user's needs;remove data from a database when such data are no longer needed; andperform other such data management operations.

DCL 232 is a part of a database language 226 used by a system designeror another to: provide protection of, and security for, stored data frommisuse, misappropriation, corruption, and destruction; grant, manage,and revoke access privileges to users for accessing a database system orparticular segments of a database system; provide other controlfunctions such as preserving database integrity for particular datatransactions and providing backup in event of system failures; andperform other such data management operations. Insofar as the SCR systemand method may be implemented using a database software system anddatabase language suitable to a particular application environment for aparticular SCR embodiment, the particular commands and instructions foreffecting such implementation are specific to the particular databasesoftware system and, therefore, are not herein described.

An embodiment of SCR database 220, therefore, may receive a plurality ofdata: as may be declared by users via a communications network 1802,1804, 1806, 1808 and, in particular instances, via the aid of a userinterface 224; and as defined, manipulated and controlled via databasesoftware 222 and database language 226. SCR database 220 may store suchdata as particular classes of data and as particular instances of datawithin a particular class. Data in SCR database 220 may be furtherorganized into entities 234, attributes 236, unique identifiers 238 andentity relationships 240. As also illustrated in FIG. 18, SCR database220 may include tables 242, forms 244, queries 246, and reports 248.

Although not illustrated in FIG. 18, one of skill in the art willappreciate that the systems disclosed herein may exist in a cloudcomputing network. For example, the SCR database 220 may exist on anumber of distributed data stores and/or servers, such as Web Servers1808 that are located in a number of different locations. The varioustypes of data and SCR components disclosed herein may be stored acrossthe distributed data stores and or servers that make up a cloudnetworked SCR database. Client devices, such as devices 1802, can accessthe various devices that make up the cloud via a network, such asnetwork 1806. One of skill in the art will appreciate that network 1806may be the Internet, a WAN, a LAN, or any other type of network known tothe art.

FIG. 19 is a block diagram illustrating an exemplary embodiment of anSCR application 1800 in an environment wherein SCR database 220 mayreceive data from either of, or both, an enterprise data system and aglobal data synchronization network. For instance, an embodiment of SCRmay be used in an environment in which particular data regarding objectsexisting in sequential chains may already exist in existing enterprisedata systems 1902 such as accounting systems, inventory managementsystems or any ERP system, such as those provided by SAP AG, IBM® orOracle® Corporation. Similarly, an embodiment of SCR may be used in anenvironment in which particular data regarding objects existing insequential chains may already exist in one or a plurality of global datasynchronization networks 1904, or GDSN, such as the GDSN® that isinteroperated with the GS1 Global Registry.

In such an application environment, wherein SCR system and method 1800may be interoperated with either or both an enterprise system 1902 and aGDSN 1904—referred to herein, collectively, as external datanetworks—SCR database 220 may receive data via a network 1802, 1804,1806, 1808 and database software 222, as described above, but wherebydata stored in such external networks is first manipulated via asuitable user interface 224, for instance, via an interface that mayenable data extraction, transformation, and load (also, herein referredto as ETL) operations. Integration of data supplied by external datanetworks 1902, 1904 and received by SCR database 220 may execute withinthe same operating environment as database software platform 222, asdescribed above. Alternatively, data integration may executeindependently from software platform 222, that is, on separatecomputers. In either event, such data integration enables SCR database220 to receive data from one or more external networks 1902, 1904 inaddition to receiving data from users communicating directly with SCRdatabase 220, as described earlier.

FIG. 20 and the additional discussion in the present specification areintended to provide a brief general description of a suitable computingenvironment in which the present invention and/or portions thereof maybe implemented. Although not required, the embodiments described hereinmay be implemented as computer-executable instructions, such as byprogram modules, being executed by a computer, such as a clientworkstation or a server, including a server operating in a cloudenvironment. Generally, program modules include routines, programs,objects, components, data structures and the like that performparticular tasks or implement particular abstract data types. Moreover,it should be appreciated that the invention and/or portions thereof maybe practiced with other computer system configurations, includinghand-held devices, multiprocessor systems, microprocessor-based orprogrammable consumer electronics, network PCs, minicomputers, mainframecomputers and the like. The invention may also be practiced indistributed computing environments where tasks are performed by remoteprocessing devices that are linked through a communications network. Ina distributed computing environment, program modules may be located inboth local and remote memory storage devices.

FIG. 20 illustrates one example of a suitable operating environment 2000in which one or more of the present embodiments may be implemented. Thisis only one example of a suitable operating environment and is notintended to suggest any limitation as to the scope of use orfunctionality. Other well-known computing systems, environments, and/orconfigurations that may be suitable for use include, but are not limitedto, personal computers, server computers, hand-held or laptop devices,multiprocessor systems, microprocessor-based systems, programmableconsumer electronics such as smartphones, network PCs, minicomputers,mainframe computers, distributed computing environments that include anyof the above systems or devices, and the like.

In its most basic configuration, operating environment 2000 typicallyincludes at least one processing unit 2002 and memory 2004. Depending onthe exact configuration and type of computing device, memory 2004(storing, among other things, sequential chains constructed as describedherein) may be volatile (such as RAM), non-volatile (such as ROM, flashmemory, etc.), or some combination of the two. This most basicconfiguration is illustrated in FIG. 20 by dashed line 2006. Further,environment 2000 may also include storage devices (removable, 2008,and/or non-removable, 2010) including, but not limited to, magnetic oroptical disks or tape. Similarly, environment 2000 may also have inputdevice(s) 2014 such as keyboard, mouse, pen, voice input, etc. and/oroutput device(s) 2016 such as a display, speakers, printer, etc. Alsoincluded in the environment may be one or more communicationconnections, 2012, such as LAN, WAN, point to point, etc.

Operating environment 2000 typically includes at least some form ofcomputer readable media. Computer readable media can be any availablemedia that can be accessed by processing unit 2002 or other devicescomprising the operating environment. By way of example, and notlimitation, computer readable media may comprise computer storage mediaand communication media. Computer storage media includes volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information such as computer readableinstructions, data structures, program modules or other data. Computerstorage media includes, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other medium which can be used tostore the desired information. Communication media embodies computerreadable instructions, data structures, program modules, or other datain a modulated data signal such as a carrier wave or other transportmechanism and includes any information delivery media. The term“modulated data signal” means a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, and not limitation, communicationmedia includes wired media such as a wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared and otherwireless media. Combinations of the any of the above should also beincluded within the scope of computer readable media.

The operating environment 2000 may be a single computer operating in anetworked environment using logical connections to one or more remotecomputers. The remote computer may be a personal computer, a server, arouter, a network PC, a peer device or other common network node, andtypically includes many or all of the elements described above as wellas others not so mentioned. The logical connections may include anymethod supported by available communications media. Such networkingenvironments are commonplace in offices, enterprise-wide computernetworks, intranets and the Internet.

Data Analysis Module

As described above and illustrated with FIGS. 18 and 19, an embodimentof the SCR system and method may include a data analysis module 1810.Such data analysis module, for instance, may include software with arange of data mining tools, deep statistical analysis tools and methods,parsers, etc. The following paragraphs describe exemplary data outputcreated via data mining (or similar data analysis) tools for anexemplary embodiment of SCR in the oil and gas industry.

FIG. 21 is an embodiment of a user interface illustrating data output(as shown in screenshot 2100) from a data analysis module, which may beincluded in an SCR embodiment for the oil and gas industry. In thisexemplary data output, a decision tree data mining algorithm 2102 hasoperated on relational data created in an SCR database. Aninterpretation of such data output, in this instance, may be as follows.A petroleum refiner has purchased (or is considering purchase of) aplurality of crude oil cargoes from a plurality of oil suppliers 2104.Each cargo is from a particular source country. Each country has aparticular third-party rating for a country parameter (as an example ofdata type-4, an attribute of a SC component host entity), such as for ameasure of reported fiscal transparency, which has been received by andstored in an SCR database. (A non-limiting example of such a measure isthe Corruption Perceptions Index, or CPI, published periodically byTransparency International, a transparency organization.) The datamining tool, in this instance, has computed on the data pertaining tosuch transparency measure for the plurality of cargo instances and hasreturned a decision tree 2106 based on computed data histograms.Relational information such as that illustrated in FIG. 21 may provideutility to an SCR user, for example, in making relative comparisons forparticular attributes associated with the source (e.g., the country inthis illustration) of material inputs purchased—or which may bepurchased—at a particular point in a sequential chain. Such relationalinformation, as may be queried by a user and returned (in response to auser query) by the SCR system and method and specifically by the SCRdatabase holding the data elements enabling formation of such relationalinformation, may be managed within such database as follows. First, andreferring to FIG. 15, such database may receive data via the nature ofdata input form 1500, or otherwise via other data input methods, via thedata communications methods as described elsewhere herein. Second, andonce such data input has been received by the database, a data analysismodule 1810 as shown in FIGS. 18 and 19 may be used to perform datamanipulation, e.g. statistical analyses or creation of relational datadisplays amongst different classes of data or information that may be ofuse or interest to users. Third, as shown in data object 2106 in FIG.21, as output from such relational data analysis, classes of data may beemployed in order to create relationships amongst the dynamic data thatpertains to objects transiting through sequential chains (for instance,crude oil moving in large lot quantities through global petroleum supplychains) and other data that may be associated with such dynamic object,or product, data such as data pertaining to the degree of fiscaltransparency reported by an independent body for the particularcountries from which particular lot quantities of crude oil may beproduced. The latter nature or class of data, unlike the dynamicobject-related data (such as quantities of crude oil lots, as objects orproducts) may be, as in this instance just described, relatively morestatic data, for instance data that may remain fixed annually such asthe Corruption Perceptions Index, or CPI, data annually disclosed byTransparency International. Thus, a benefit of the SCR system and methodto users may often be its capability to provide to users and others theoften more static data or information, such as attribute valuespertaining to features of particular SC components or SCC host entities,and to relate or associate (via computational techniques, performed in adata analysis module 1810 in FIGS. 18 and 19) such static data to themore dynamic data pertaining to the objects, e.g., products themselvesthat transit sequential chains.

FIG. 22 is a screenshot 2200 illustrating other nature of exemplary dataoutput from a data analysis module, shown as element 1810 in FIGS. 18and 19, which may be included in an SCR embodiment for the oil and gasindustry. In this exemplary data output, carbon dioxide (or CO₂)emissions are reported as tons per million British thermal units (tonsCO₂/mm BTU) 2204 for production (from crude oil input), transport anddelivery of gasoline. In embodiments, it may be observed that such dataoutput 2200 portrays the data attribute of CO₂ emissions 2208 for eachof ten SC components 2202—from SC component no. 2220, the El Morgancrude oil field, through SC component no. 2222, tank trucks deliveringgasoline to petrol service stations. CO₂ emissions are also ranked 2206,in this instance, from the highest CO₂-emitting SC component (e.g., theoil field that produces El Morgan crude oil) to the lowest CO₂-emittingSC component (e.g., the feed pipelines that charge crude oil to a crudeoil distillation unit). The exemplary data output also shows each SCcomponent's relative contribution 2208 to total CO₂ emissions in theform of a bar chart. Relational data such as that shown in table 2200may be of use to gasoline consumers, for instance, in comparing unit CO₂emissions levels across a plurality of gasoline brands. Such data mayalso be of use to crude oil producers, refiners, oil tanker operators,regulators, and others, for instance, in evaluating operationalperformance in efforts to reduce emission levels or to meet regulatoryrequirements. For instance, of particular current interest to officials,oil producers and investors in the Province of Alberta, Canada is the“well-to-wheel” emissions content for various, different factors (suchas CO₂ and sulphur) as well as the water consumption, as these areemitted or used in producing crude oil (for downstream refining of crudeoil into refined products such as gasoline and diesel fuel) for crudeoil derived from Alberta's vast resources of oil sands and how such datacompares to comparable data attributes for other crude oil sources, e.g.for crude oil produced in Texas, Trinidad and Venezuela. While recenteconomic studies have been performed to illustrate such bench-scalecomparisons of particular data attributes for various alternative crudeoil sources, as compared to data for Alberta's oil sands resources, theSCR system and method, using a data analysis module, may enableconsumers and regulators to track actual, physical quantities of crudeoil through their complex supply chains, as one example of a sequentialchain, and thereby gain a statistical comparison of particular dataattributes at the point of consumption (e.g. at the gas pump) inconnection with or in advance of purchasing a particular brand ofgasoline derived from a particular type and source of crude oil. Theforegoing, therefore, provides the reader an example of the SCR systemand method's capability to associate static data, for example, datapertaining to a relatively stable oil refining process (as an example ofa SC component), with the dynamic data that may be associated with theproduct (as an example of an object transiting a sequential chain)itself. Such relational data for different classes of data and forvarying degrees of data transience (e.g., dynamic versus static data)may be created within an SCR system via various combinations of datainput and analysis techniques, as herein described.

In an embodiment, the data analysis module 1810 as shown in FIGS. 18 and19, may compute an ‘SCR score.’ An SCR score may be computed based on aset of particular publicly disclosed measures. In an exemplary instance,measures selected as components of a customizable SCR score are threedifferent metrics pertaining to sustainability: i) a measure of EITImembership, reflecting a weighted average (with ‘yes’ as 100 percent and‘no’ as zero percent) of all the countries' EITI membership conditionfor the countries comprising Enterprise A's and B's respectivequantities of crude oil produced in a given period; ii) a similarweighted average for countries' transparency rating by TransparencyInternational; and iii) a similar weighted average for countries' UNhuman development index or HDI. For instance, enterprise ‘A’ may haveproduced 725.6 million barrels in a particular time period. By weightingeach of the producing countries' three sustainability measures by theirshare of enterprise A's total crude oil production, and applying aformulaic weighting of each such measure, an SCR score of 78.2 isobtained for ‘A.’ For the exemplary instance, the following illustrativeformula is used to obtain the indicated SCR score: SCR score={[EITIvalue]+10*[TI rating]+100*[UN HDI]} divided by 3.0.

Although specific examples of computing an SCR score have been provided,one of skill in the art will appreciate that other manners of scores maybe computed. In embodiments, the SCR score may be adapted to aparticular industry, a particular sector in an industry or to any otherdomain.

Sequential Chain Monitoring

Embodiments of example uses of the SCR systems and methods disclosedherein will now be provided. In one such embodiment, the systems andmethods disclosed herein may be employed to track products, as a form ofobject, as they traverse a supply chain. By connecting to an SCRdatabase over a network, such as the Internet, data about a product canbe captured as the product moves through a supply chain. As will beapparent to an artisan of ordinary skill, an SCR database may receivedata input from one or a plurality of authorized users and others,depending on factors such as the size of an organization deploying anSCR embodiment, the geographic dispersion of the organization, theinternal configuration of the organization, the number and nature ofenterprise and other data systems employed by the organization, and aplurality of other factors. Although, for clarity, all exemplaryembodiments of SCR described herein employ such decentralized data entrymode, it will be apparent to an artisan of ordinary skill that fully orpartly centralized data entry modes may alternatively be used forenabling an SCR database to receive data. Also, it is noted that the SCRsystem and method employs a plurality of data types. As describedearlier herein, data type-4 is defined as data pertaining to SCcomponent host entities. As such, and given that SCC host entities mayrelate to a geographic or positional attribute of SC components—forinstance, to a country, state, province, or other such geographicattribute or to many or all of such geographic attributes in ahierarchical manner—a system facilitator, or another, apart from theenterprise or other organization deploying SCR, may provide data entrywith respect to data type-4 (SCC host entity data objects). As earlierherein described, SCC host entity data attributes and data values oftenmay be of a relatively static nature and less transient ortime-sensitive than may be data pertaining to objects that transitdynamically through sequential chains. Such relatively more staticnature of SCC host entity data may be one reason, amongst others, whyparties, organizations, persons or another, other than system users,suppliers and customers, are appropriate for enabling an SCR database toreceive such relatively static data. That is, such SCC host entity data,when they are relatively static, may be received less frequently (forinstance, monthly or annually) from a neutral body overseeing such SCChost entity data, whereas data pertaining to objects and SC componentsare more transient in nature and generally are more amenable to beingreceived dynamically—for instance, in real- or near real-time—by an SCRdatabase from enterprise users or other appropriate system users.

FIG. 23 is a block diagram illustrating flows of data, as received byand returned from an SCR database 220 for an embodiment of the SCRsystem and method in the global, integrated oil and gas industry. Themethod by which data is communicated between the SCR database and aplurality of system users and others is as described herein.

Upon completion of construction of a database model and correspondingdatabase structure 220, as shown in FIG. 23 and as described hereinabove, authorized users (or, as also used herein, users) in the oil andgas industry (for this exemplary embodiment) commence operation of theSCR system and method by defining database entities. A database entitycorresponds to an actual entity—for instance, ‘object,’ ‘SC component,’or ‘enterprise’—for which a user or another wishes to assign a uniqueidentity and to keep track of in some manner. In common database usage,entities are often thought of as nouns, e.g. ‘enterprise’ or ‘SCC hostentity.’ (Examples of data pertaining to database entities received bySCR database 220 are described above and with FIG. 2.) SCR database 220receives data relating to specification of a database entity by a user:i) selecting a data entry form, such as data entry form 1500, shown inFIG. 15 and described above, wherein such data entry form will havealready been created (as part of the system construction process,described herein earlier) as a data object and stored in SCR database220; ii) entering appropriate data into such data entry form; and iii)transmitting the completed data entry form to the database 220. Theexemplary SCR embodiment for the oil and gas industry may, as oneexample, include use of the Internet as a selected data communicationsmode of operation and use of web browsers as a method for user interfacebetween users and the SCR system and method. Therefore, an artisan ofordinary skill will understand that, in this exemplary embodiment, auser (102, 104): may access an appropriate data entry form from SCRdatabase 220 via the internet, using a web browser and a user interface224; completes the data entry form within the web browser, for instance,by using a desktop computer or laptop computer; and enables the databaseto receive the completed data entry form via the internet and using aweb browser. As also will be apparent to an artisan of ordinary skill,alternative means of enabling a database 220 to receive data input maybe used, such as via mobile phone or PDA 1802. The following paragraphsdescribe more particularly the manner in which database entities anddatabase entity relationships are received by SCR database 220 for anembodiment of SCR in the oil and gas industry.

FIG. 24 illustrates an exemplary problem concerning a sequential chainparticipant's—in this instance, a petroleum refiner's—presumedimperative need for a particular type of information and how the SCRsystem can solve such a problem. In this figure, box 2400 illustrates anexemplary oil and gas industry supply chain, as a particular nature ofsequential chain, wherein such supply chain may be comprised of sevenexemplary SC components, e.g., SCC no. 2410 through SCC no. 2424 in thefigure. Focus of this exemplary problem, which the SCR system can solve,is on the last SC component, e.g. on a petroleum refiner—and,particularly, on assumed information needs of such exemplary petroleumrefiner. For instance, a petroleum refiner may be required by law orregulation in a particular country to demonstrate that crude oilprocessed in the refining company's particular petroleum refinery hasnot been procured in such manner as to benefit known corrupt oilproducing countries. The U.S. Dodd-Frank Act 2010 contains such aprovision with respect to minerals extracted from the DemocraticRepublic of Congo, or DRC. Thus, for exemplary purposes, the informationneed, for instance, may be stated as: “A refining company (operating ina particular country, herein referred to as a ‘processing country’) isrequired to prove that crude oil processed in a refinery within suchprocessing country did not originate, e.g., was not sourced, from acountry (herein referred to as a ‘source country’) that is considered toexhibit known characteristics of corruption, as may be evidenced byspecific metrics,” for instance, as such characteristics may be inferredfrom the corruption perceptions index, or CPI, which is periodicallydetermined and widely published by the international organizationTransparency International (www.transparency.org/). Embodiments of theSCR system enable acquisition of such information, as described next,thereby providing a solution to this exemplary information problem.

FIG. 24 illustrates a sequential chain 2400, also referred to as asupply chain (and, sometimes, as a value chain), through which a lotquantity of crude oil—as an example of what herein is referred to as anuncovered object, as earlier described—may transit and ultimately bereceived by an exemplary petroleum refiner at SC component no. 2424, atwhich component a refiner may process such crude oil into a plurality ofpetroleum products, including, for instance, naphtha, gasoline, dieselfuel, fuel oil, and asphalt. In this example, the exemplary petroleumrefiner, employing an embodiment of the SCR system, is required toensure and prove that crude oil charged to processing units in itspetroleum refinery in a given processing country has been sourced fromsource countries that are not considered to be corrupt countries, e.g.,pursuant to a presumed law or regulation.

First, the exemplary refiner may actualize, via an SCR database, arepresentation of the sequential chain depicted in FIG. 24 by employingthe object-centric chain mode, illustrated in FIG. 4, thus enabling anSCR database to receive and organize data in a relational manner, thusenabling association of a plurality of data within and across all sevenof the exemplary SC components illustrated in FIG. 24. For instance, byusing the SCR system's object-centric chain embodiment or mode, a systemuser may create in an SCR database a relational data set, such as thatshown in the exemplary database table 2402. Thus, FIG. 24 illustrateshow a plurality of SC components in an exemplary oil and gas industrysequential chain, represented by the set of pictures, may beconceptualized as a series of SC components, which, in turn, may berepresented as discrete instances in a database table 2402, which may bestored in an SCR database, using methods as herein earlier described.For instance, the illustrative database table 2402 may be understood asincluding data pertaining to a set of seven SC components—starting withthe El Morgan oil field, SCC 2410, and concluding with the petroleumrefiner's refinery, SCC 2424—and with an uncovered object, that is, alot quantity of El Morgan crude oil, transiting in a particular sequencefrom the first to the seventh exemplary SC component. The exemplaryobject of ‘crude oil,’ as an example of an uncovered object, means, forclarity, that such object (as it would be comprised of possibly billionsof particular hydrocarbon molecules) is incapable of having associatedwith it (that is, with each of such exemplary billions of molecules) anexisting form of object unique identifier such as an RFID or a barcode.

Next, the exemplary petroleum refiner or another may declare a pluralityof data, which may be received by an SCR database as earlier described,and which may be joined or related via the mechanisms and methodsdescribed herein. As herein earlier described, these methods include: i)an SCR database enabling data association within a particular SCcomponent, herein referred to as vertical logical conjunction, orrelation, of data; and ii) an SCR database enabling data associationamongst a plurality of SC components, herein referred to as horizontallogical conjunction, or relation, of data. Also as herein earlierdescribed data received and stored by an SCR database may include dataof a plurality of data types, including, for instance, data pertainingto: an object; a sequential chain; SC components, which comprise asequential chain; SCC host entities, which host SC components; and otherdata, including various forms of data object identifiers. In the presentexemplary instance, a petroleum refiner situated at SC component no.2424 in supply chain 2400 in FIG. 24 may include particular data, interalia, data pertaining to a host entity that hosts SC component 2424. Inparticular, the petroleum refiner needs information, available to it atSC component 2424, e.g., at the processing country, wherein suchinformation pertains to particular attributes of the SCC host entitythat hosts SC component 2410, e.g., data relating to certain corruptionperceptions ratings of the crude oil-source country. As described hereinearlier, data pertaining mainly to an enterprise's entities—includingobjects, sequential chains, and SC components—may be declared into anSCR database by the enterprise or another, whereas data pertainingmainly to an SCC host entity, which hosts an SC component, may (but neednot) be declared into an SCR database by a system facilitator, theenterprise, some neutral party, or another.

The mechanisms herein described, including vertical logical conjunctionand horizontal logical conjunction, enable the exemplary refiner at SCcomponent no. 2424 in FIG. 24 to access, via an embodiment, the targetinformation relative to the SCC host entity that hosts SC component2410, e.g., to information pertaining to measures or indicators ofcorruption (or to absence of corruption or to degree of corruption)relevant to the source country. To ensure that such informationpertaining, in this exemplary instance, to the first SCC host entity(that is, to the host entity hosting SC component no. 2410 in the sourcecountry) is accessible to the refiner at the last SC component (that is,the refinery, as SC component no. 2424, located in the processingcountry), it suffices that an embodiment of the SCR system enables dataassociation for data in any SC component (n) to data in any other SCcomponent (n−1) and/or (n+1), so long as: i) the target data (e.g., inthis instance, data pertaining to ratings for perceptions of corruptionat the origin, that is, at the SCC-1) for the first SCC host entity are,in fact, received by, stored and manipulated in, and accessible from theSCR database; ii) there is not a break in the sequence of SC componentswithin the SCR database, e.g., there is a continuous connection, withoutgaps, amongst each SC component with each adjacent such component; andiii) a user at the last SC component has access to the relevant datacontained in the SCR system, including to the relevant data pertainingto the first SCC host entity. An embodiment of the SCR system, asdescribed herein, provides these and other capabilities, therebyenabling the exemplary petroleum refiner to demonstrate—e.g. toregulators in the processing country, which hosts SC component no. 2424in the sequential chain 2400—the source origin of crude oil refined (orto be refined) at the petroleum refinery and, therefore, to demonstrateparticular attributes that describe the SCC host entity, includingattributes that can be used to calculate measures of the sourcecountry's ratings pertaining to corruption and to other features. Aswill be apparent to one of skill in the art, there may be instances inembodiments wherein continuous connection of data across a set of SCcomponents, as described above, may not always be necessary. Forinstance, in an embodiment, particular data may be received into an SCRdatabase (e.g., data pertaining to SCC (4) 2418) whereby some othermeans of forward-linking such data to a downstream SCC (e.g., SCC (7)2424) may be used (e.g., a user transmitting such data via facsimile)such that the data may still be preserved in the SCR database andappropriately related at the downstream SCC even though the data may notbe preserved in the SCR database at the upstream SCC.

As previously described, in embodiments, a DocString identifier may becreated and associated with each component of the sequential chain. TheDocString identifier is modified as each piece of data is added to thesequential chain. In embodiments, the modification may be in the form ofconcatenating the unique identifier of each component of the chain tothe DocString identifier. By doing so, the DocString identifier containsinformation that can relate each component of the sequential chain,thereby identifying a relationship between all data in the chain thatmight otherwise be siloed in individual, proprietary enterprise systems.

As herein later below described, embodiments also provide—via a conceptof ‘point of defined dilution’—for the circumstance wherein a gap in asequential chain does occur, whereby system users may still obtain dataand information at SC components downstream of such a gap and whereinsuch data may be provided as statistical data (e.g., data expressed witha measured degree of uncertainty, for example, by use of ‘significance’metrics). Such sequential chain gaps may occur, for instance, when oneparty in the chain is not a participant in a particular embodiment. Forinstance, referring to FIG. 24, the owner or operator of the fourth SCcomponent 2418, an oil tanker, may not initially be a participant in anembodiment operated by an enterprise or group of enterprises operatingthe remainder of sequential chain 2400. In such instance, the operatoror operators of the remainder of the entire sequential chain 2400 mayrequire the operator of SC component 2418, the oil tanker, to cooperateby participating, in at least a minimum degree by declaring particulardata input to an SCR database, or else to lose the business opportunityof transporting crude oil via a component, or segment, in the sequentialchain 2400. Alternatively, the operator or operators of the entiresequential chain 2400 may accept the non-cooperation of the operator ofSC component 2418, the oil tanker, and employ the concept of ‘point ofdefined dilution,’ thereby diluting the level of certainty of data andinformation at the SC component causing the gap in the chain andthereafter. As will be apparent to an artisan of ordinary skill, thecompleteness of information content pertaining to objects and the SCcomponents in which objects exist may be greater when all SC componentsin a given sequential chain are included and, likewise, less when someSC components are excluded from the scope of the complete sequentialchain, as such scope may be reflected in the data content of an SCRdatabase in a particular embodiment. As described above for an exemplaryinstance in the petroleum industry, embodiments are capable of solvingthe problem of how to provide relational information concerning objectsand the sequential chains (and their SC components) that objects transitfor uncovered objects, such as lot shipments of crude oil. The SCRsystem, therefore, is shown to have capability to help track otherwiseuntraceable lot shipments of crude oil and, by extension, of othernature of uncovered objects. Although current oil and gas industrypractice often provides for identifying crude oil origins from source upto a petroleum refinery, further examples described below show how suchidentity information—along with a plurality of other attributes—may betracked by embodiments even after crude oil is refined into a pluralityof petroleum products, that is, after a resource input has been consumed(for instance, by the process of petroleum refining) and no longerexists in the form that it once had at its origin.

FIG. 25 illustrates a sequential chain, such as a supply chain in theoil and gas industry, by which crude oil may be produced and moved via aplurality of SC components, and then refined into gasoline, or petrol,and marketed to final customers. The first seven components shown inFIG. 25, as comprising parts of sequential chain 2400, are identical tothose illustrated in FIG. 24. That is, these seven SC componentsrepresent: production of El Morgan crude oil, at SCC 2410; storage andtransport of such crude oil via SCCs 2412 through 2422; and refining ofsuch crude oil at SCC 2424, a petroleum refinery. FIG. 25 includes acontinuation of the sequential chain 2400 by listing additional SCcomponents situated downstream of the exemplary refinery. Thus, FIG. 25portrays representation of an extensive oil industry supply chain—alsoreferred to as a ‘well to wheel’ supply chain and as a value chain—bywhich crude oil may be produced, transported, and refined into petroleumproducts and whereby such products are stored, transported, and marketedto final consumers. The entire set of 11 illustrative SC components inFIG. 25 may comprise a single sequential chain, herein also referred toas a proprietary sequential chain, or PSC. Alternatively, the 11 SCcomponents may be formed as two or more PSCs, joined by one or morelinking changes of control action (or CCAs), into a mixed sequentialchain, or MSC. The terms PSC, CCA, and MSC are as herein earlierdescribed. For instance, the set of seven SC components in 2400 mayrepresent one uniquely identified sequential chain, as a PSC, and theset of the final three SC components in 2400—SCCs no. 2428, 2430, and2432—may represent a second uniquely identified PSC, whereby SCC no.2426 acts as a CCA linking together the two PSCs into one MSC (that is,as a ‘linking CCA,’ as earlier described). This example illustratesanother capability of the SCR system and method, that of facilitatingdeep data relationships even in circumstances wherein the supply chainmanagement (‘SCM’) software systems employed by one enterprise (e.g. bythe enterprise responsible for the PSC comprised of SCCs no. 2410through 2424) and another enterprise (e.g. by the enterprise responsiblefor the other PSC shown in the latter stages of FIG. 25) may bedisparate systems, for example a system vended to one enterprise byOracle and a system vended to the other enterprise by IBM. Often vendorsof particular SCM systems attempt to ensure that their SCM customersremain tied to the particular vendor by employing highly specific systemcoding and other features to help foster a ‘silo’ nature of relationshipbetween the SCM vendor and the customer.

Although specific embodiments of analysis data have been provided withrespect to a specific industry, e.g., the oil and gas industry, one ofskill in the art will appreciate that the data analysis module (shown aselement 1810 in FIGS. 18 and 19) may perform other industry-specificanalysis. The sequential chain components described herein may be usedwith any type of data related to any industry, thereby allowingdifferent industry-specific analysis to be performed on an object as ittraverses a sequential chain. Similarly, the construct of an SCR score,as earlier herein described, may also be tailored in a highlycustomizable fashion, for instance, with respect to any of: an industry;an industry sector; an enterprise; a group of enterprises; and others.

For example, the SCR systems and methods described herein may be used totrack food products as they travel through a supply chain. By leveragingthe sequential chains described herein, the supply chain for aparticular food item may be provided. For example, an apple may beidentified, by scanning its bar code (which may, in some instances, notbe applied until late in a particular sequential chain that ends withthe apple being sold in a store), entering its shipping identification,etc. Upon identifying the food item (e.g., the apple) the sequentialchain associated with the food item may be retrieved from a database,such as an SCR database. The sequential chain contains data identifyingthe specific traversal of the food item (e.g., the apple) from itsorigin (e.g., the apple orchard) through every intermediary up until itsfinal retail destination (e.g., a grocery store). Such information maybe provided to consumers who are concerned about the source of theirfood, the carbon foot print of their food purchase, or for any otherpurpose.

Assembly Chain Monitoring

The SCR systems and methods disclosed herein may also be applied to theengineering and construction industries. As used herein, the termengineering and construction refers to any or all of a plurality offunctions performed in the areas of design, engineering, procurement,construction, commissioning, maintenance and similar or relatedfunctions, whereby a product is assembled from a plurality of componentparts, units, segments or the like and whereby the product may becomprised of a plurality of sub-assemblies. By way of example but notlimitation, products assembled in the engineering and constructionsector, as herein defined, include: tangible objects such as an offshoredrilling platform, an automobile, and an airplane; and intangibleobjects such as a computer program, a suite of legal contractspertaining to financing, construction, ownership and operation of atrans-national oil pipeline, and an assembly of financial securitiescomprising a package of securitized debt obligations. Thus, the finalproduct formed by processes functioning in the assembly mode ofoperation—for assembled products, either tangible or intangible innature—is comprised of a plurality of objects, which may transit througha plurality of sequential chains, which may converge at a common pointof assembly or sub-assembly.

An SCR embodiment in the engineering and construction sector may operatein a SCR's assembly chain mode while supply chain embodiments describedherein may operate in an embodiment referred to as SCR's object-centricmode, as earlier described. This distinction is illustrated in FIG. 26.In the object-centric operation mode of an SCR embodiment—e.g., in theexemplary oil and gas industry embodiment—an SCR database 220 receivesand manipulates data pertaining to an object or objects that transitthrough, and may be changed within, a particular sequential chain—forinstance, object 2602 as it enters sequential chain 2604 and a relatedobject 2618 as it exits the same sequential chain 2604. In the assemblymode of operation of an SCR embodiment—e.g., in the engineering andconstruction embodiment—an SCR database 220 receives data for objects asthey transit sequential chains and then continue to receive datapertaining to a plurality of objects 2618, 2634, 2652 as these objectsfurther proceed to be included in a final, assembled object (or insub-assemblies included in a final, assembled object).

A final assembled object 2654 in FIG. 26—for instance, an offshore oilproducing platform, a petroleum refinery, a subsea oil pipeline, amotorway, or an assembled automobile—may be comprised of a plurality ofobjects, e.g., objects A, B, and C 2602, 2620, 2636. In assembly mode ofoperation, as employed for an SCR embodiment in the engineering andconstruction sector, such objects commence their transit of a particularsequential chain, e.g., SCs 2604, 2622, 2638 as object forms 2602, 2620,2636. Forms of objects at commencement of sequential chains may be thesame or different from the object 2618, 2634, 2652 forms existing atconclusion of those sequential chains. For instance, sequential chain2604 in FIG. 26 may be a pipe coating plant or facility, wherein a setof homogeneous objects A 2602—e.g., discrete sections of steelpipe—enters the sequential chain at SC component 2606 and exits thesequential chain at SC component 2614, whereby the objects (via the SC)may be treated and coated with protective materials prior to beingassembled [e.g., as assembled object G 2654] into a finished sub-seapetroleum pipeline.

Each sequential chain 2604, 2622, 2638, as illustrated in FIG. 26, mayexist in form similar to that illustrated in FIG. 4, whereby asequential chain may be comprised of a plurality of SC componentsbeginning and ending with a process activity and with a change ofcontrol action between each adjacent pair of process activities. Asearlier herein described, logical structures other than the structure ofalternating one process activity (or PA) and one change of controlaction (or CCA), as adjoining SC components, may also be employed. Thealternating (PA)-(CCA) structure, as illustrated in FIG. 4, is usedherein as one exemplary logical structure, with an accompanyingtaxonomy, by which data may be structured and organized in a database ofan embodiment. Other logical structures may also be employed inembodiments. For instance, a user, system designer, or another may wishto implement an embodiment wherein no distinction is made between PAsand CCAs, perhaps instead using only ‘stages,’ or ‘STGs’ herein, as alocus of activity at which something occurs with respect to an objectlocated within a given STG. Another instance of a user-specified logicalstructure that differs from the (PA)-(CCA) structure herein describedmay be one in which a user, system designer, or another may wish toimplement an embodiment wherein each pair of STGs, as just described,may be considered as a single sequential chain—that is, wherein thelogical structure used is: {[STG₁]-[STG₂]} representing a sequentialchain, which may further be linked to other such sequential chains. Manydifferent such logical structures and accompanying taxonomies may beemployed in embodiments, depending on users' needs, applicationenvironment, and other factors.

Sequential chains in an SCR embodiment for the engineering andconstruction sector may include both PSCs and MSCs, as illustrated inFIG. 11. As shown in FIG. 26, an SCR database 220 receives datapertaining to all of: objects 2602, 2618, 2620, 2634, 2636, 2652, 2654;sequential chains 2604, 2622, 2638; SC components 2606 through 2614,2624 through 2632, 2640 through 2650; SC host entities (not illustratedin FIG. 26); and other elements (also not illustrated in FIG. 26). Asdescribed earlier and with FIG. 4, a particular taxonomy may be employedto aid in creating a data schema for use in constructing and operatingan SCR embodiment in the engineering and construction sector. Asdescribed herein, the taxonomy used in describing the engineering andconstruction sector embodiment is the same as used earlier hereindescribing the oil and gas industry embodiment. However, SCR taxonomiesneed not be the same for different embodiments of the SCR system andmethod and may be constructed to suit the needs and circumstances of aparticular application environment. Even users in the same particularapplication environment, perhaps having different particular needs andinterests, may employ different schema and taxonomies.

FIG. 27 shows a representation of the three exemplary, discretesequential chains illustrating how such sequential chains in thepipeline engineering and construction industry—operating in theassembly-mode of SCR operation, as earlier described—relate to oneanother, enabling completion of a finished object 2708. In thisexemplary instance, such finished object 2708 may be considered as theentire pipeline, engineered, constructed and brought to fruition via aset of distinct sequential chains 2702, 2704, and 2708, functioningtogether in the assembly-mode of SCR operation.

Although specific examples are provided with respect to Assembly ChainMonitoring, one of skill in the art will appreciate that the embodimentsdisclosed herein are not limited to the specific examples provided. Forexample, the SCR systems and methods disclosed herein may apply to otherareas such as, automotive, general manufacturing, computer software andhardware, or any other industry, service or the like in which thecreation of products occurs in a sequential manner. In embodiments, thedata output from the assembly chain mode may be similar to the otherforms of output described herein.

Combined Chain Mode

The assembly chain mode is an embodiment, such as that herein earlierdescribed for application in sectors such as the engineering andconstruction industry and sub-sectors, whereby users may wish to focuson assembly of a completed object—for instance, of an offshore drillingplatform or a pipeline as used in the oil and gas industry—that may becomprised of a plurality of particular objects and sub-assemblies. Theobject-centric chain mode is an embodiment such as that herein earlierdescribed for application in sectors, such as the oil and gas and otherextractive industries, whereby users may wish to focus on transit ofobjects (such as large lot quantities of hydrocarbons) throughparticular sequential chains. As also earlier herein described, users ofembodiments employing the assembly chain mode or the object-centricchain mode further may wish to focus on data and information pertainingto the informational milieu of the sequential chains through whichobjects transit, including, for instance, on such milieu as may relateto: SC components that comprise sequential chains, SC component hostentities that host SC components, and other information. A third form ofSCR embodiment is that which may be constructed by using, incombination, one or a plurality of sequential chains operating in theSCR's object-centric chain mode plus one or a plurality of sequentialchains operating in the SCR's assembly chain mode. Such thirdoperational mode, or embodiment, of the SCR system and method is hereinreferred to as the combined chain mode or embodiment. One example of anindustry in which a combined chain mode may be utilized is the financialservices industry.

FIG. 28 illustrates a plurality of sequential chains 2804, 2810, 2818,2830, 2832, 2834 that, together, function in SCR's combined chain mode.Each such chain is comprised of a plurality of SC components, by whichobjects, for instance, objects in the financial services sector, maytransit from origin to destination. These sequential chains operate bothin assembly chain mode [sequential chains 2804, 2810] and inobject-centric chain mode [sequential chains 2818, 2830, 2832, 2834].Thus, these sequential chains, taken together, may be considered tooperate in the combined chain mode, or embodiment, of the SCR system andmethod.

By way of example but not limitation, the nature of objects in afinancial services environment such as illustrated in FIG. 28 mayinclude: objects A 2802, 2806 and objects B 2808, 2812, which in thisfigure may represent a plurality of particular corporate or projectloans; object C 2814, which may represent a set, or package, of suchloans that is assembled from the particular project loans and which isreferred to herein as collateralized debt obligations or CDOs; objects2822, which represent a plurality of subsets, or slices, of such packageof CDOs; and object D 2824, object E 2826, and object F 2828, whichrepresent a plurality of particular subsets, or slices, of CDOs. Thefollowing paragraphs describe a manner in which SCR's combined chainmode of operation, or embodiment, may be employed to track and tracesuch financial objects through a plurality of sequential chains and tocapture and make available relational information pertaining to suchfinancial objects and to the sequential chains in which they exist orexisted. As will be apparent to an artisan of ordinary skill, financialobjects transiting sequential chains, wherein such objects may betransformed in nature—e.g., by processes known as securitization andpartitioning into tranches, or sub-sets, of partitioned loans—representa set of processes similar to that herein earlier described forresource-transformation industries such as the oil and gas industry.That is, financial objects that transit sequential chains, which operatein SCR's combined chain mode, or embodiment, may be either covered oruncovered objects and may undergo transformations within one or aplurality of such sequential chains such that financial objects exitingsuch chains may be changed in form in relation to such objects' formupon entering such chains. Thus, as with the other embodimentapplication environments herein described, the nature of problemaddressed via SCR's combined chain mode of operation, or embodiment, isone of preserving and making available data and information pertainingto objects that transit sequential chains functioning in the combinedassembly and object-chain modes and to the environments in which suchobjects exist.

Movements of financial securities, as objects, through the referencedsequential chains, as just described, may occur as follows; later,below, a concrete example is illustrated. An enterprise may form objectD 2814, that is, a package of CDOs, first by assembling a plurality ofparticular loans G 2806 and H 2812 via sequential chains 2804, 2810.Operating in this manner, these sequential chains 2804, 2810, takentogether, represent the assembly chain mode of operation within thefinancial services embodiment of SCR, analogous to the assembly chainmode herein earlier described for the engineering and constructionsector. Once such a package of project or corporate loans 2814 isassembled—for instance, representing a collective face value of $30billion—the enterprise may process such package of loans via sequentialchain 2818, operating as shown in FIG. 28 in the object-centric chainmode, analogous to the chain mode herein earlier described for the oiland gas sector. For instance, in sequential chain 2818, such package ofloans, as a group, may pass through a plurality (q) of SC componentswhereby: the composite package is partitioned, or sliced, into aplurality of particular risk categories; each such risk category, orslice, of the original package of loans is evaluated; and the pluralityof such slices then prepared for distribution to customers in financialmarkets. SC component (q) 2820, as one SC component in sequential chain2818, may operate as a split platform (as this form of SC component isdescribed herein and with FIG. 9), whereby a plurality of CDOtranches—object D 2824, object E 2826, and object F 2828—are created,with each such CDO tranche then being distributed, respectively, viasequential chains 2830, 2832, 2834.

As has been described, above and with FIG. 28, a manner in which an SCRembodiment in the financial services sector, functioning in SCR'scombined chain mode, may enable: assembly, via sequential chains 2804,2810 functioning in assembly chain mode, of a set of project orcorporate loans 2814 from a plurality of discrete loan obligations 2802,2808; processing of the set of loans 2814, via sequential chain 2818functioning in object-centric chain mode into particular risk-ratedtranches, or subsets, of such set of loans; and sale of such tranches2824, 2826, 2828 via a plurality of distribution chains 2830, 2832,2834, each operating in object-centric chain mode. The foregoingdescription illustrates the originate-and-distribute method ofoperation, combined with securitization, employed by a plurality offinancial institutions in existing financial markets. Operations such asthese in the residential mortgage sub-sector known as sub-primemortgages were a principal contributor to the financial crisis of2007-2009. Use of an SCR embodiment, operating in the combined-chainmode as herein described, may have enabled players in the sub-primemortgage industry to have maintained better monitoring of the actual,atomic level of risk contribution made by each portion of eachindividual sub-prime mortgage contained in the financial instrumentseventually sold into markets as tranches of the securitized, partitionedcomponent mortgages. The ability, via SCR, to preserve such atomic-levelrisk data may be contrasted with the more aggregated risk ratingsassigned to these complex financial securities by rating agencies suchas Moody's and others. In this respect, wide use of SCR's combined-chainmode or embodiment may have enabled avoidance of potentially asubstantial portion of the multi-trillion dollar losses encounteredduring and since the financial crisis of 2007-2009. In privatecommunication during 2011 with the inventor, an analyst at the New Yorkbranch of the Federal Reserve Bank has indicated that the capacity ofSCR [that is, via its combined-chain mode of operation] to trackintermediated risk would be a huge benefit.

While FIG. 28 and the foregoing description illustrate a financialservices embodiment of SCR employing a particular configuration ofsequential chains operating in both the assembly chain mode and in theobject-centric chain mode, it will be apparent to an artisan of ordinaryskill that, alternatively, other configurations of sequential chains mayalso be used, as may be appropriate to circumstances and objectives in aparticular application embodiment.

FIG. 29 provides an example of data analysis that may be performed in acombined chain mode. For such illustrative purposes, an actual database,comprised of hypothetical data, has been created with the followingfeatures, as summarized in table 2902 in FIG. 29: i) two loanoriginators, ‘J’ and ‘K,’ who originate 16 project loans (named ‘A’through ‘H’ and ‘S’ through ‘Z’) with total face value of $30 billion;306 discrete loan tranche sets, of which 137 contain loan tranchespartitioned from loans originated only by originator ‘J’ and 169 withloan tranches partitioned from loans originated only by originator ‘K;’a total of 1,393 partitioned loan tranches, representing an average of4.55 loan tranches per tranche set and an average face value of $98million per partitioned loan tranche; data input, with respect to sevenattributes 2904 of the 16 discrete project loans, whereby values foreach such attribute are normalized to continuous variables and on a1-to-100 scale where ‘1’ is worst and ‘100’ is best; and data input of aunit price 2906 for each tranche set, whereby such unit price is indexedto a scale of zero to $100 per unit and where the average unit price is$59.54 for the group of 306 tranche sets.

Two other independent variables, as one form of data output, arecomputed from six of the seven independent (input) variables 2904 listedin FIG. 29: i) a weighted value, herein referred to as ‘SCR score 1;’and a second weighted value, herein referred to as ‘SCR score 2.’ Thesetwo SCR score indices, each including weighted values for threedifferent independent variables, may be computed within an SCR database220, as shown in FIG. 18, or within a data analysis module 1810, as alsoshown in FIG. 18. Considerations of computational speed, data transferspeeds and other factors may favor such computational operations beingdone within either the database element 220 of an embodiment or withinthe data analysis module element 1810 of an embodiment. Construction ofthe two forms of SCR score is described next, with reference to the sixexemplary independent variables (2910 through 2920) in FIG. 29 andwherein the symbols ‘V,’ ‘X,’ ‘Y,’ ‘Z,’ ‘AA,’ and ‘AB’ have the meaningsshown for these six variables. While the attributes SCR score 1 and SCRscore 2 may be considered as dependent variables—e.g., variables thateach are dependent on three particular independent variables—hereinthese two representations of multi-dimensional SCR scores are consideredas independent variables (e.g. with respect to tranche price) that arederived from other independent variables as data inputs.

SCR score (1), in the exemplary combined chain embodiment within thefinancial services sector, is computed as follows:

“ SCR ⁢ ⁢ Score ⁡ ( 1 ) ” = { ⌊ ( V ) + ( 2 * X ) + ( 3 * AB ) ⌋ } .Thus, by this exemplary, non-limiting example of an equation, SCR score(1) may be understood to represent a composite measure, with respect toa particular tranche set (and to the underlying loans for loan tranchesincluded in a particular tranche set), such as tranche set Alpha-1constructed from the following three independent variables: i) aproject's sponsors' average senior debt rating, ‘V’ 2910, with respectto all the sponsors of a particular project that receives project loans,which are originated by either originator ‘J’ or ‘K;’ ii) a measure ofthe project's interest coverage, ‘X’ 2912, e.g. an average of the firstfive full operating years' estimated before-tax cash flow cover ofaverage estimated before-tax interest expense; and iii) a measure ofestimated quality of product offtake arrangements, ‘AB’ 2920, whereinthese three variables are normalized to a 1-to-100 scale. As will beapparent to an artisan of ordinary skill, with these three particularindependent variables, SCR score 1 may be viewed, for instance, asrepresenting a composite measure that reflects a set of factors thatdescribe aspects of the overall health of a project—e.g., from acombined operating and financial perspective—wherein the project isassociated with particular loans, which may be partitioned into loantranches and included in a particular tranche set.

SCR score (2) 2908 in the exemplary combined chain embodiment within thefinancial services sector, is computed as follows:

${``{{SCR}\mspace{14mu}{{Score}(2)}}"} = {\left\{ \frac{\left\lfloor {\left( {1.5*Y} \right) + (Z) + \left( {3*{AA}} \right)} \right\rfloor}{5.5} \right\}.}$Thus, by this equation, SCR score 2 may be understood to represent acomposite measure, with respect to a particular tranche set (and to theunderlying loans for loan tranches included in a particular trancheset), such as tranche set Alpha-1 constructed from these the followingthree independent variables: i) a host country rating, ‘Y’ 2914, withrespect to the country that hosts the project, which receives projectloans that are partitioned into loan tranches—for instance, a relativecountry rating such as that which may be published by a financialinstitution or by the United Nations; ii) a measure of the quality ofthe project's insurance coverage, ‘Z’ 2916, e.g. pertaining to theextent of cover for particular assets and for business interruptionrisks; and iii) a measure of protection afforded to the project byvirtue of IFIs' participation, ‘AA’ 2918, wherein these three variablesare normalized to a 1-to-100 scale. As will be apparent to an artisan ofordinary skill, with these three particular independent variables, SCRscore 2 may be viewed, for instance, as representing a composite measurethat reflects a set of factors that describe aspects of the overallhealth of a project—from a perspective of external bodies' views of theproject's host country and of insurers' willingness to insure againstparticular risks associated with the project—wherein the project isassociated with particular loans, which may be partitioned into loantranches and included in a particular tranche set.

Thus, the exemplary SCR scores, as herein described for an embodiment inthe financial services sector, may include, for instance: i) a scorethat indicates a single, composite measure of the estimated overallfinancial health of the project itself (e.g., SCR score 1), whereby suchmeasure may be of interest to parties considering purchase of securitiessuch as those described above for this example embodiment; and ii)another score that indicates a single, composite measure of theestimated overall political or macroeconomic health of the country thathosts the project (e.g., SCR score 2), whereby such measure may also beof interest to such parties. As will be apparent to an artisan ofordinary skill, such scores or indices like the ones described hereinfor SCR score 1 and SCR score 2 may be constructed in a plurality ofmanners, depending on factors such as the perceived needs of systemusers, the requirements of regulators, and other factors; or, suchcomposite scores or indices may not be constructed. The availability ofmulti-dimensional scores or ratings, such as those described herein forSCR score 1 and SCR score 2, may be of considerable additional benefitto financial market participants, customers, regulators and othersinsofar as these scores may supplement the ratings provided by ratingagencies. The capacity of such SCR scores to provide such supplementalrisk information is created via SCR's capabilities for accessing,retaining and using atomic-level risk measures associated with, forexample, individual sub-prime mortgages that enter into complexorigination-and-distribution chains at the furthest upstream stage (thatis, SC component) in such chains, that is, at the stage or componentwhere discrete, individual sub-prime mortgages are originated. Theunavailability of such atomic-level risk information at the intermediateand downstream stages (that is, SC components) of the sequential chainsthat originated, processed and sold complex financial instruments, suchas those just described above, is widely reported in the globalfinancial press to be one of the core causes of the global financialcrisis of 2007-2009. To the extent that “markets mispriced risk,” asdeclared by former Federal Reserve Bank Chairman, Alan Greenspan, inofficial testimony, such mispricing of risk may have been in large partdue to market players having lost track of the atomic-level risk ofindividual sub-prime mortgages as such risk accumulated (withoutaccurate, continued measurement) at the downstream stages of thefinancial industry chains by which complex, securitized sub-primemortgages were (and still are) created. That is, the mispricing of risk,as averred by Alan Greenspan may, in large part, have been attributableto markets and market players having lost track of risk due to theinability of the financial industry to track attributes, such as risk,continuously through the complex business chains characterizing thatindustry. SCR's systems and methods can solve this problem.

FIG. 30 is a flow chart illustrating an embodiment of a method 3000 forproviding information to a user about an object (e.g., a covered or anuncovered object) as it transits a sequential chain. Flow begins atoperation 3002, where information about a first object is received. Inembodiments, a first object may be any type of tangible or intangibleobject that traverses a sequential chain. In embodiments, the firstobject is related to a sequential chain by a unique identifier that isassociated with the sequential chain. For example, the unique identifiermay be a DocString identifier as disclosed herein.

Flow continues to operation 3004, where a first data item is received.The first data item may be any type of data related to the object as ittraverses a sequential chain. For example, the first data item may beany type of data related to the sequential chain components, thesequential chain component host entities, or other objects disclosedherein. In one embodiment, the first data item may be a trade document(or may be gathered from a trade document) as described herein.

In embodiments, the first object may be related to the first data itemusing a unique identifier, e.g., a DocString identifier or other uniqueidentifier as described herein. Although not shown in FIG. 30, themethods described with respect to FIGS. 16 and 17 may be employed withFIG. 30 to create a SCR component and/or relationships described herein.

Flow continues to operation 3006 where the method 3000 identifies atleast one attribute of the first data object. For example, the firstdata object may have multiple attributes (e.g., entity name, hostcountry, purity score, etc.) In embodiments, the multiple attributes maybe stored collectively (e.g., in one SCR component). In otherembodiments, each attribute may constitute an individual data item. Insuch embodiment, each attribute may be stored collectively orindividually (e.g., as multiple SCR components such as, for example,multiple sequential chain host entities). In embodiments, only someattributes may be used to calculate a score for the object and/orsequential chain. In such embodiments, these attributes are identifiedat operation 3008.

At operation 3008, a score is calculated based upon the one or moreidentified attributes. In one embodiment, an algorithm may be deployedat operation 3008 to calculate the score. For example, the purityattribute may be modified depending on other data from the sequentialchain (e.g., splitting or blending the object). In such embodiment, anyof the algorithms disclosed herein or any other algorithm related to thespecific object, the object's associated industry, or sequential chainmay be employed at operation 3008. One of skill in the art willappreciate that multiple types of algorithms may be employed atoperation 3008.

In another embodiment, information may be retrieved from an externalsource (e.g., another database, a third-party, etc.) at operation 3008.In such embodiments, the information used to calculate the SCR score maybe stored in a centralized repository, and attribute data stored in theSCR system may be used to retrieve such information. Examples of suchinformation include, but are not limited to, data related to the childlabor practices of a country, the purity of oil from a specific countryor well, the carbon produced by the facility that manufactured theproduct, etc. In embodiments, the attribute identified in operation 3008may be used to query the external source for the score, or informationthat may be used to calculate the score. For example, if one of theattributes identified at operation 3006 is the country “China”, datarelated to China's carbon emissions may be retrieved at operation 3008from a third party, such as the UN. The retrieved data may itselfcomprise the score calculated at operation 3008, or it may be furthermodified by an algorithm to produce a score. In addition, attribute datamay also be used to query for information within the SCR system tocalculate a score.

Flow continues to operation 3010 where the method 3000 receives arequest for data about features of a sequential chain. In embodiments,the request may include the unique sequential chain identifier. In otherembodiments, the request may include an identifier associated with anobject. In such embodiments, the sequential chain may be identified byits relation to the object. For example, as described herein, aDocString identifier may be modified to include the identifier of thesequential chain, an object, and all sequential chain components andsequential chain component host entities related to the object. In suchembodiments, the sequential chain may be identified by the DocStringidentifier. For example, in one embodiment a user may scan a barcodeattached to a tangible item to receive information about the item'straversal of a sequential chain. For example, a user in a grocery storemay scan a bar code affixed to a sticker on an apple. The bar code is anobject identifier of the apple that may be sent to a SCR system toidentify a related sequential chain. In further embodiments, the requestmay also include a request for specific data about the sequential chain.For example, the user may be interested in the carbon footprint of theobject, the country of origin of the object, etc. As such, the type ofinformation related to the sequential chain may be specified at therequest received at operation 3010. By using the SCR system, the usermay be able to retrieve information about the apple that was collectedbefore the bar code was affixed to the apple.

Flow continues to operation 3012. At operation 3012, the method 3000provides the score to the user. For example, at operation 3012, themethod 3000 may gather information about the object, such as the firstdata item received at operation 3004, using the established relationshipbetween the object and the data item as described herein. For example,the relationship may be identified based upon a unique identifier, suchas, but not limited to the DocString identifier. Upon identifying therelated information, the related information may be provided to the userat operation 3012.

In further embodiments, the method 3000 may filter the sequential chaindata score or modify the sequential chain data score before providingthe sequential chain data score at operation 3012. For example, if thesearch request identified a specific type of information (e.g.,information related to a carbon footprint, the purity of the product,etc.) operation 3012 may perform a filter operation such that only therequested type of sequential chain data score, rather than all thesequential chain data, is returned at operation 3012. In still furtherembodiments, an algorithm may be employed on the sequential chain dataat operation 3012 in order to produce the requested information atoperation 3010.

Although method 3000 is described as only receiving a first data item,one of skill in the art will understand that any number of data itemshaving any number of attributes (and those attributes' associatedvalues) may be received by operation 3000. Furthermore, in embodiments,the method 3000 may be used with blend platforms, split platforms,change platforms or combinations of these. One of skill in the art willappreciate the method 3000 may be employed to calculate and provide ascore for any type of sequential chain using any type of data related toan object traversing the sequential chain.

Although specific embodiments were described herein and specificexamples were provided, the scope of the invention is not limited tothose specific embodiments and examples. One skilled in the art willrecognize other embodiments or improvements that are within the scopeand spirit of the present invention. Therefore, the specific structure,acts, or media are disclosed only as illustrative embodiments. The scopeof the invention is defined by the following claims and any equivalentstherein.

What is claimed is:
 1. A system comprising: at least one processor; andmemory encoding computer executable instructions that, when executed bythe at least one processor, perform a method for identifying datarelated to a first object traversing a first sequential chain and asecond object traversing a second sequential chain, the methodcomprising: receiving a first data item related to the first object, thefirst data item having a first identifier; modifying a first DocStringidentifier using the first identifier, wherein the first DocStringidentifier represents the first sequential chain; receiving a seconddata item related to the second object, the second data item having asecond identifier; modifying a second DocString identifier using thesecond identifier, wherein the second DocString identifier representsthe second sequential chain; determining that the first object iscombined with the second object to create a combined object; modifyingthe first DocString identifier with the second DocString identifier tocreate a combined DocString identifier, wherein the combined DocStringidentifier identifies a third sequential chain that comprises the firstsequential chain and the second sequential chain; and providinginformation relating to the combined object.
 2. The system of claim 1,wherein the first data item includes attribute information about thefirst object.
 3. The system of claim 2, wherein the first data item is asequential chain component, wherein the sequential chain componentcomprises data representing the movement of the first object as ittransits through the first sequential chain.
 4. The system of claim 1,wherein modifying the first DocString identifier comprises concatenatingthe first DocString identifier with the first identifier.
 5. The systemof claim 1, the method further comprising: receiving a third data item,the third data item having a third identifier; modifying the combinedDocString identifier based at least in part upon the third dataidentifier; and identifying a relationship between the first, second,and third data items using the combined DocString identifier.
 6. Thesystem of claim 5, wherein the third data item is a sequential chainhost entity, wherein the sequential chain host entity comprises datapertaining to an entity that is related to at least a particular portionof the third sequential chain.
 7. The system of claim 1, wherein thefirst data item is received from a first user at a first location andthe second data item is received from a second user at a secondlocation.
 8. The system of claim 7, wherein the second location isdifferent from the first location.
 9. A system comprising: at least oneprocessor; and memory encoding computer executable instructions that,when executed by the at least one processor, perform a method ofconstructing a sequential chain to track an object as it moves across aplurality of enterprise systems, the method comprising: receiving firstdata from a first enterprise system, the first data item having a firstidentifier; modifying a first DocString identifier using the firstidentifier, wherein the first DocString identifier represents thesequential chain; determining that the first object is split into asecond object and a third object, wherein the second object isassociated with a second identifier and the third object is associatedwith a third identifier; creating a second DocString identifier based atleast upon the first DocString identifier and the second identifier,wherein the second DocString identifier represents a second sequentialchain; creating a third DocString identifier based at least upon thefirst DocString identifier and the third identifier, wherein the thirdDocString identifier represents a third sequential chain; and providinginformation on the second and third objects.
 10. The system of claim 9,wherein the first data item includes attribute information about thefirst object.
 11. The system of claim 9, wherein the first data item isa sequential chain component, wherein the sequential chain componentcomprises data representing the movement of the first object as ittransits through the first sequential chain.
 12. The system of claim 9,wherein the method further comprises: receiving second data from thefirst enterprise system, wherein the second data system relates to thesecond object; and modifying the second DocString identifier based atleast in part upon the second data.
 13. The system of claim 12, whereinthe method further comprises: receiving third data from a secondenterprise system, wherein the third data relates to the third object;and modifying the third DocString identifier based at least in part uponthe third data.
 14. The system of claim 12, wherein the first enterprisesystem is different from the second enterprise system.
 15. Anon-transitory computer storage medium comprising computer executableinstructions that, when executed by a processor, perform a method ofidentifying data related to an object traversing a first sequentialchain and a second object traversing a second sequential chain, themethod comprising: receiving a first data item related to the firstobject, the first data item having a first identifier; modifying a firstDocString identifier using the first identifier, wherein the firstDocString identifier represents the first sequential chain; receiving asecond data item related to the second object, the second data itemhaving a second identifier; modifying a second DocString identifierusing the second identifier, wherein the second DocString identifierrepresents the second sequential chain; determining that the firstobject is combined with the second object to create a combined object;modifying the first DocString identifier with the second DocStringidentifier to create a combined DocString identifier, wherein thecombined DocString identifier identifies a third sequential chain thatcomprises the first sequential chain and the second sequential chain;and providing information relating to the combined object.
 16. Thenon-transitory computer storage medium of claim 15, wherein the firstdata item and the second data item include attribute information aboutthe first object, and wherein the provided information comprises a scorebased on the attribute information.
 17. The non-transitory computerstorage medium of claim 15, wherein the first data item includesattribute information about the first.
 18. The non-transitory computerstorage medium of method of claim 17, wherein the first data item is asequential chain component, wherein the sequential chain componentcomprises data representing the movement of the first object as ittransits through the sequential chain.
 19. The non-transitory computerstorage medium of method of claim 15, wherein modifying the firstDocString identifier comprises concatenating the first DocStringidentifier with the first identifier.
 20. The non-transitory computerstorage medium of claim 15, the method further comprising: receiving athird data item, the third data item having a third identifier;modifying the combined DocString identifier based at least in part uponthe third data identifier; and identifying a relationship between thefirst, second, and third data items using the first combined DocStringidentifier.
 21. The non-transitory computer storage medium of claim 20,wherein the third data item is a sequential chain host entity, whereinthe sequential chain host entity comprises data pertaining to an entitythat is related to at least a particular portion of the third sequentialchain.